When I received the registration email, it was not in plain text like it was for v 1.3.2. It was formatted, though in what I don't know. Because of that, the URL isn't automatically hyperlinked because it doesn't have HTML markup telling it is a link. Also, there are no line breaks.
This is a registration email sent from v 1.4.1 (The hyperlink is from the forum, but it's not like that in Outlook):
QuoteThank you for registering at Take Thu Your username is : "test" Your password is : "****" In order to activate your account, you need to click on the link below or copy and paste it in your web browser. http://localhost:84/register.php?activate=5d8aa3bf223da1e928f7bf2b2322825a Regards, The management of Take Thu
This is from v. 1.3.2:
QuoteThank you for registering at Take Thu!
Your username is : "test"
Your password is : "****"
In order to activate your account, you need to click on the link below
or copy and paste it in your web browser.
http://localhost:85/register.php?activate=17b23b84f6d577d75425ea5ec5ed5b5f
Regards,
The management of Take Thu!
Is it related to this (http://forum.coppermine-gallery.net/index.php?topic=11155.msg50447#msg50447)?
yes, I'm afraid so.
Joachim
I tried Nibbler's suggested fix and the format looks the same. :-\\
However, that code was supposed to fix another issue which I did not have.
My registration emails have line breaks :-\\
I was hoping it would be due to my setting for Character encoding but when I changed it from Western to Default, it didn't make a difference. :-\\ And I have run CVS update to ensure I am using the most recent unaltered (by me) files.
So I guess it's down to server setup, but it works with v. 1.3.2 and I ran a diff to compare the files and can't seem to find the difference that would affect things like this.
The difference would be in the mailer. Adding nl2br()s into some places should fix the formatting problems.
does anybody volunteer to fix this?
Joachim
I have encountered and resolved the same thing while working on the report to moderator function so I'll give this a try.
I tested it out and it looks like it had already been fixed or addressed so will mark this accordingly.