dabeebe2000

Sorry, just saw these posts as were going in my promotions folder.

But I don’t have any additional details. I found an article somewhere talking about problems with object cache and I believe BuddyPress in general, and then someone on WPMU recommended to look at that as well as they had heard of general issues with it and provided a link (but that link really had no useful information). All I can say is with regard to how WP-Engine implements it this was 100% the cause. It has been working perfectly ever since it got turned off.

If you ever want me to test new code to see if it fixes it just let me know – happy to help.

Thanks, David

Okay, we swore we looked at this last night, but all of this was related to object caching on the site. I went back and checked again and it was on, and strangely it appears WP-Engine has two places that this can be turned on from, so I checked one place, saw was on, turned off and tested and didn’t work. And then a little bit later saw the second place, and turned off and it worked this time.

Okay, just wanted to give an update. I worked with WPENGINE and we did all sorts of testing, and it seems that the lines 89/90 PHP error is the only thing that is likely to be causing this issue.

This is the code:
`if ( ! isset( $all_activity_items[$sid] ) && ! empty( $sid ) ) {
$all_activity_items[$sid] = 1;`

The only thing I can think of is this is related to php or MySQL, but at this point I have no idea. I am on MySQL 5.5.42 and PHP 5.3.

I can upgrade to PHP 5.5 if I want. I do not know the version of the server I moved from (although I think I recall 5.4.x), and that server is gone so I can’t check.

So any help would be great. All other mail is sending fine using this plugin. Thanks, David

Below is what WPENGINE told me, but the more I look into it the more I think this has to do with some default setting on that I can change on the SQL side. The main reason is it takes literally 10 seconds for the “SQL reaper” to kill the query, which seems really quick if it was that big of a deal. Anyway, any help would be great appreciated.

Thanks for reaching out to support! I understand you’re having some difficulties with your email plugin sending out notifications and I’ll be glad to help out! On our platform we have mechanisms that will regulate the server from being overwhelmed with requests or tasks. This ensures that our servers performance for your site and other clients are on point at all times. I’m afraid sometimes that this can cause issues with taxing scripts that require a lot of work to fire off correctly. The one that’s playing a role here is our MySQL reaper that will kill queries that take a long time to process so it does not saturate MySQL connections on the box if there are many long running queries that can impede database performance.

What may be the option here would be to see if there is a way for the plugin to do many, smaller batches, of the request instead of all of them at once. This way the task/process will not get killed while still getting completed. I’m not too familiar with that exact plugin however there are some mail subscription plugins that do handle large list size in smaller batches. I would advise in reaching out to the plugin developer to see if they’re able to provide some insight in segmenting the size of notifications being sent out.

OH, was using and it looks you define right there. Duh…

I have tried a lot of stuff. What was interesting is when I tried going to the wp-cron link, and also changing the daily time to a few minutes away it seemed to run, but not all the way through.

I worked with my host provider and they upped memory, but I still got the same memory error.

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 64 bytes) in /home/denver/public_html/wp-content/plugins/buddypress-group-email-subscription/bp-activity-subscription-digest.php on line 109

Here is what the host provider did (and recommended), which still didn’t resolve it.

Hello,

I’ve increased the memory_limit from 64M to 128M. In addition to that I’ve created a custom php.ini in your home directory so we do not need to change the global file for future changes.

Any thoughts? I am a bit out of my league on this one.

Boone was able to resolve it. I am not sure of the specifics, but he said he is going to update the plugin to accommodate it. Thanks for the support! Amazing free plugin.