Queue not being processed since last week

I managed to fire the queue by uncommenting lines 252 and 253 in bp-activity-subscription-digest.php:

add_action( 'bp-actions', 'ass_daily_digest_fire' ); // for testing only
add_action( 'bp-actions', 'ass_weekly_digest_fire' ); // for testing only

Then visiting a buddypress page.

I’m not 100% sure, but I think the queue had become too big and was failing due to a PHP Out of memory error. This is slightly weird as everywhere seems to have the limit set to 64M but the error was implying it was only 24M. I’ve tried setting it in wp-config now so I’ll see how I get on.

It’s still not sending automatically. I’ve fired the daily digest again using the above action.

I added define( 'WP_MEMORY_LIMIT', '96M' ) in wp-config.php before it loads wp-settings.php. There wasn’t a PHP error in the error_log from this morning when the digest should have fired.

Any other ideas on how I can debug this further?

Still no joy with this unfortunately. I installed the Mail Queues plugin, which is working well in terms of the mail queueing, and when I manually fire the digests the page definitely loads quicker, but there’s still no automatic firing.

Anyone got any ideas?

Also, I now get a PHP warning when I manually fire the digest/weekly summary:

Warning: Creating default object from empty value in /wp-content/plugins/buddypress-group-email-subscription/bp-activity-subscription-digest.php on line 544

I see you are having a nice conversation with yourself.

I’m having issues with email notifications not being sent also. sometime the work sometimes not. been checking around for a solution. I think i’m going to try to find a plugin that sends out email via smtp. Saw a recommendation somewhere. worth a try.

gmail, right?

“we recommend you upgrade all of your applications to OAuth 2.0. If you choose not to do so, your users will be required to take extra steps in order to keep accessing your applications.”

https://googleonlinesecurity.blogspot.ca/2014/04/new-security-measures-will-affect-older.html

Increase you memory or max execution time in php.ini to try and fix this
These are my settings

;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 128M ; Maximum amount of memory a script may consume (32MB)
max_input_vars = 4000

Your php.ini may be found in you cgi-bin