puregraphx

@mcbart, use “contribute their code” instead. Just a tip 🙂 there != their

In all fairness guys, it is not proven that Yoast intentionally changed code to block this plugin. Also, they develop their own product and can/will not guarantee compatibility with every other plugin.

It is up to the RYSC author to make sure his plugins works with every version of Yoast, perhaps if he was able to get a sneek peak at the upcoming release code. But I believe Yoast won’t be too keen on working together 🙁

But it’s free so we can’t complain (too much) 🙂
Hope they fix it soon, will disable on all sites for now.

Indeed, we are using W3TC and DEBUG is enabled.

ini_set('log_errors','1');
ini_set('display_errors','0');
ini_set('error_reporting', E_ALL );
//define('TOOLSET_LOGGING_STATUS', 'debug');
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
define('WP_MEMORY_LIMIT', '256M');
define('DISABLE_WP_CRON', true);

any idea what to look for in the W3TC plugin? We have other sites with W3TC and DEBUG enabled, but don’t see this NextGEN issue in the debug.log.

I have no idea if this is related to the Avada theme, I can only tell you what the error reads.

[07-Nov-2017 09:38:21 UTC] We’re sorry, but your theme’s page template didn’t make a call to wp_footer(), which is required by NextGEN Gallery. Please add this call to your page templates.

In the last 10 hours, we see 92 of these entries in the debug.log
We have a dev.casaboavsita.com site if that helps you reproduce/investigate the error.

Hi,
Sorry about the long delay in response, we did not receive this error any more, but I just noticed that we disabled the plugin, sorry.
We have enabled it again, so we should be getting the error again next time cron job run, 2x a day.
These are server side crons correct, created with cPanel, WP crons have been disabled in the wp_config.

Sorry, I couldn’t say when it started, we are managing about 50 websites for our clients, we are a web agency, and it was by chance that we stumbled upon this huge (almost 500 MB) debug.log, but I can’t remember the entry date of the oldest error.

We will re-install the plugin and monitor if the issue is gone