nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwsend_mail creating irrelavant Characters.

Rathina

We are invoking the default iwsend_mail.ipl from the workflow. We have added a code wherein the path of the attached file is displayed in the email. The email is shown as HTML.
Some extraneous characters are displayed in the display path. The piece of code to display the path is -

my($serverurl) = "http://<server-name>/folder" . $serverfoldername;
$msg .= join(" ",
"<tr><td rowspan='$count'>",
"<b>Link</b></td>",
"</tr>",
"<tr><td rowspan='$count'>",
"<a href='$serverurl' target='_blank'>$serverurl</a></td>",
"</tr>");

We are using the same $serverurl in 2 places, once in the href and once to display. It appears correctly in the href but not in the display.

The path in the email looks something like -

http://<server-name>/globa !l/x.htm

The actual display should be global whereas it appears as globa !l. The ! mark keeps on changing its location. We obeserved in the 'View Source' of the email that whenever a carriage return is there in the source code it puts an ! mark at the end of that line.

Any ideas as to why this is happening?

TS 5.5.2 on Win2K.

Thanks in advance
-Rat

Find more posts tagged with

Comments

Jeremy

Hi,

Seen this before. Check this post - I think it points to another post with the answer.

http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=DOWNLOADS_WORKFLOWS&Number=16941&page=&view=&sb=&o=&vc=1

HTH

Jeremy

Adam Stoller

the quick-fix is to change:
join("", ...);
to:
join("\n", ...);
and that should probably resolve the problem. If it doesn't, let us know.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Rathina

The '\n' Character solves the problem.

Thanks.

abhishek_gupta

Has Interwoven done something about it? If the message goes through several reviews/rejections then its likely that the message would become quite huge. Hence putting a single \n would not work. Its better if we put \n in more than 1 place.

Adam Stoller

I think the Interwoven solution has mostly been towards moving away from iwsend_mail.ipl and towards iwsolutions_mail.ipl (which I still haven't played with since iwsend_mail.ipl does pretty much everything I've needed thus far).

One of these days I might take the time to re-write iwsend_mail.ipl as primarily a Perl Module with a simple interface on top of it....

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com