Hi,
could you please upgrade to version 4.3.2.1 and see if that solves the problem?
Thank you,
Jason
Version 4.3.2.1 is already installed, the issue is occurring with that version.
The main difference between 4.3.1 and 4.3.2(.1) is a new version of browscap and other minor bug fixes that should not affect wp_cron in any way. We ran some tests on our end, and the cron was triggered without any problems. Also, we have the latest version of Slimstat running on our official website, and we have cron jobs to generate daily reports, and everything seems to be working as expected. It must be some kind of conflict maybe, or a PHP memory limit error? The new Browscap database is about 10% bigger than the previous one. Maybe that’s causing WP to hit your php memory limit during the cron?
The memory limit is currently set to 256 mbs. Is that sufficient?
With WP_DEBUG & WP_DEBUG_LOG set to true we’re not getting any notifications of memory limit problems in our logs.
The only error that’s logged when a scheduled post misses it’s schedule (with slimstat activated) is as follows,
PHP Notice: Object of class WP could not be converted to int in /wp-content/plugins/wp-slimstat/wp-slimstat.php on line 229
Have you tested scheduling a post with the plugin activated?
Hi, would you be available to test a bugfix? Contact us and I will send you a copy of the new version: http://support.wp-slimstat.com
Thank you,
Jason
File sent. Keep us posted.
