-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'From:' header string running together on Apache server #92
Comments
Thank you for sanity checking this. It has been flagged before and when the penny eventually dropped the plugin has been patched and a new release made. Does that version work? |
No, that was my first attempt at a fix -- just upgrading to the latest version (4.7.1). But the issue still happened. I edited the plugin code for that version as mentioned above, and then things started working perfectly. If there's any more info I can provide that would be helpful, let me know. |
Hmmm, that is strange. And annoying. What is the setting of If there is something we can latch onto and determine what conditions trigger this behaviour, we can code around it. |
Hi @Bloke , here's the TXP Diagnostics info (minus 'private' information):
Other than that the only thing I can say is that something must've changed in my client's server environment to cause the problem...she is on Hostgator. We had not made Textpattern core or plugin updates of form changes when it started happening, I think in early March. |
Hi All, my client whose site is using com_connect recently flagged an issue where the From: field had a bunch of stuff in it, not just a clean email address. For example:
It seemed like the "From" header string was not being separated properly. When I changed these lines:
$sep = IS_WIN ? "\r\n" : "\n";
to be$sep = IS_WIN ? "\r\n" : "\r\n";
(ie, a carriage return and newline character no matter what) the issue was resolved. Here is the server info:Now, those header lines look like:
So, for me I think this issue is fixed but posting here for others.
The text was updated successfully, but these errors were encountered: