kbaldac

Managed to get changes in the code ok and tested with UTF off and on

Seemed to make no difference

We appreciate your persistance but as long as we keep UTF off , the only time we get a problem is if a member uses double quote in the topic title. This happens rarely so we can live with it

Karen

This code appears to have an error in it – the { below is flagged

if ( function_exists('mb_encode_mimeheader') )
{

I am not a very experienced php coder, so don’t know what is wrong – I used copy and paste from your email

karen

We use the standard Unix mail server supplied by Krystal.

Karen

To Alexmustin – I think you just need to set UTF encode off

Sorry for delay in reply
Our system is on Krystal web site I think our domain is running on a litespeed web server running CloudLinux OS.

Karen

PS My own mailbox is gmail (sorry about typos)
Karen

Unforunately I got form teh second suggestion (commented out)
Subject: =?UTF-8?Q?Notification:=20=20re:=20Testing=20=E2=80=9CGD=20bbPres?= =?UTF-8?Q?s=20Toolbox=20Pro=E2=80=9D?=

First suggestion was the same except that it omitted Subject

Karen

Unfortunately neither of these changes seemed to make any difference to the problem we have when double quotes are used as topic titles (UTF code is off)

Example Notification: re: Testing “GD bbPress Toolbox Pro&#8221

our topic is “Testing GD bbPress Toolbox”

Karen ( pro Kim)

Apologies! My follow-up notifications were going to the new webmaster and I didn’t get them. We found there were differences in our web team because one person was using eM Client which worked with UTF-8 turned on. I use BT Mail and get ‘garbage’ with UTF-8 turned on. We also checked GMail which doesn’t work with UTF-8 turned on.

When UTF-8 is turned off, the only problems we’re aware of are special characters (as you described above). Do you still need examples? I believe it’s displaying the html codes for the special characters.

I first got these errors I think in December when Smush had the release that broke WooCommerce. The errors showed up for multiple plug-ins on our site. When a new release of Smush came out, we re-activated Smush and WooCommerce worked but finally at the end of January, we gave up due these errors continuing and de-activated Smush again. I was hoping that this latest release would fix the issue but the notes on this forum indicate otherwise.

At the time, I recollect that other plugins were getting the error when trying to find the current screen id I think at the time the scripts were being enqueued (or something like that). Turning off Smush made the errors go away.

Vinny,

We went back to 1.18.4 and get the same problem exactly if UTF-8 encoding is turned on:

Fatal error: Maximum execution time of 120 seconds exceeded in /wp-content/plugins/bbpress-notify-nospam/bbpress-notify-nospam.php on line 916

Only one no-reply@<domain name> email in the email log, rather than the 50 or so expected ones. All works fine if we turn off UTF-8 encoding.

Possibly, I had UTF-8 encoding turned off on our production system and then enabled it at some point. Thanks.

Kim

Vinny,

Just to let you know that both 1.18.5 and 1.18.6 are working again as long as we turn off UTF-8 encoding in the subject line. As a separate issue, we found that not all of our notifications were being delivered due to email volume limits set by our host. Thanks for all your very rapid help.

Kim

Will do.

php 5.6 and WordPress 4.9.8 with a Genesis framework.

Thanks Vinny. It’s not the extended time interval that stops it from crashing. When UTF-8 is turned on and there’s a single quote in the subject line, I get the topic being put into the forum but also I get:

‘The server encountered an internal error or misconfiguration and was unable to complete your request for .’

and I get:

Fatal error: Maximum execution time of 360 seconds exceeded in /wp-content/plugins/bbpress-notify-nospam/bbpress-notify-nospam.php on line 918

(this would time out at 120 seconds before the timeout interval was increased)

And the email log only gets 1 notification (rather than the expected 50 or so) that is sent to no_reply@<domain name> with the content of the topic submitted on the forum.

With UTF-8 turned off and a single quote in the subject line (same forum), I get the topic being put into the forum, the forum ‘submit’ completing in reasonable time and the 50 or so expected notifications being written to the email log. I still need to track down where they went to but there is no system error or crash and the notifications are at least being generated as reflected in the email log.

I will have my host reduce the extended time interval back to what it was since the time interval was not the problem, it just was a result of the code executing endlessly when UTF-8 encoding was turned on. However, should I have real timeout problems in future, I’ll keep in mind the alternative to wp-cron. It’s just not the solution for the problem I’m having at present. It concerns me that I can’t roll back to a version where this doesn’t happen but hopefully I can continue to avoid the problem by keeping UTF-8 encoding switched off.

Our mailing is through our host and we have logs to track it down. I’ll let you know when I find what happened to the notifications! Thanks.

Kim

Vinny,

I think we’re making some progress. We turned on email logging and our host substantially increased the timeout interval and, although the system still ‘crashed’, we got a different error message that pointed us in another direction. It appears that the UTF-8 encoding setting, which I think the plug-in may default to ‘on’, is causing a problem on one of our forums that has a single quote in the subject line of notifications.

We’ve now turned off the UTF-8 encoding and the system is no longer crashing. We can see in the email log that the system thinks notifications are now being sent, however we haven’t yet received any of the notifications and we’re working on tracking them down. If you have any ideas on this, let me know.

We know we’ve got problems with 1.18.5 and 1.18.6. Do you think we should try rolling back to 1.18.4 or an earlier version (if so, which one)? Thanks.

Kim