Why was the blank emails on registration closed? Why was the blank emails on registration closed?
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Why was the blank emails on registration closed?

Started by Dankriss, August 02, 2010, 06:37:14 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Dankriss


As what I did solved the problem I was having...ie getting blank emails on registration...as too why it solved the problem I have no idea but it did... :)

Kriss  :)
Good with HTML and CSS but no good with script... so please bear with me.. :)

cyberdyne2

I was wondering the same re: the thread.  :-\

Regarding the unfinished english_gb file: I emailed the author a few days ago and he assured me the file was complete, despite it ending with no closing .php tags ( ?> )
v.1.5.22

cyberdyne2

And att: Phill.

FWIW, I appreciate the thread was going off topic and that you guys are all very busy but let's be honest, these issues do not appear to be getting dealt with officially so it's hardly surprising when users start speculating as to the cause of their mass-faults with the script.
v.1.5.22

phill104

Who did you email? Which dev do you think wrote the file?

The thread was closed because it was going off topic. The original poster was dealing with one thing and others came in with different problems. As we have a one question per thread policy I felt it ime to close the discussion. Please start individual threads regarding your own issues.
It is a mistake to think you can solve any major problems just with potatoes.

cyberdyne2

Quote from: Phill Luckhurst on August 02, 2010, 06:41:19 PM
Who did you email? Which dev do you think wrote the file?

The thread was closed because it was going off topic. The original poster was dealing with one thing and others came in with different problems. As we have a one question per thread policy I felt it ime to close the discussion. Please start individual threads regarding your own issues.

I emailed the author, whose name was listed in the file itself: Tom Atkinson, aka Nibbler
v.1.5.22

phill104

You were lucky to get get a response as the team do not usually respond outside the forum. Nibbler is a top man.

I'll move this thread out of the email section as it really shouldn't be here.
It is a mistake to think you can solve any major problems just with potatoes.

cyberdyne2

OK.
I just asked him if 1) he thought the file was definitely complete, 2) if the file size was correct and 3) if he thought that file was the cause of the issues.
His answers were, 1) yes, 2) yes and 3) he doubts it very much.
:)
v.1.5.22

Dankriss


So getting blank emails on registration has nothing to do with emailing?

Now I am totally confused....as changing the language file has solved the problem I now get registration emails with the subject and body of the email correct.

Kriss  :)
Good with HTML and CSS but no good with script... so please bear with me.. :)

cyberdyne2

All I am saying is that the author of the file had confirmed there are no issues with that particular file. That's all.
v.1.5.22

Luc Lannoo

I had the same error on my gallery using Dutch language.

After analysis in found that the code is not the same in Dutch then in English.

In Dutch language file I found :
$lang_register_php['approve_email'] = <<<EOT
Een nieuwe gebruiker met de gebruikersnaam "{USER_NAME}" heeft zich geregistreerd in jouw galerij.
Om je account te kunnen activeren moet je op de link hieronder klikken of kopieer en plak het in je webbrowser.

<a href="{ACT_LINK}">{ACT_LINK}</a>

EOT;

In other languages I found :
$lang_register_approve_email = <<< EOT
A new user with the username "{USER_NAME}" has registered in your gallery.
In order to activate the account, you need to click on the link below or copy and paste it in your web browser.

<a href="{ACT_LINK}">{ACT_LINK}</a>

EOT;

After correcting it as in the English file it worked.

Hope this helps

Nibbler

That's actually a different issue, but thanks for reporting. I'll fix that for the next release.