We’re sorry, but your theme’s page template didn’t make a call to wp_footer()

I have cheered too soon. I repeated the same steps on the live site and after about 10 minutes, the debug.log started getting many entries again:

“We’re sorry, but your theme’s page template didn’t make a call to wp_footer()”

I can confirm this. It seems to be quiet on front-end page requests. Any ajax, rest or dashboard page request triggers this error.

@puregraphx – Did this start with a recent update to the Avada theme? This may be a case of something they have done as this error message/check has been in NextGEN Gallery for a very, very long time as it is required to have the wp_footer call (we test for it due to enqueuing scripts there).

Thanks!

– Cais.

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.

@puregraphx – Unfortunately, I am unable to reproduce a standard/default Avada installation that produces these entries. Can you provide and additional details that might point to this being within NextGEN Gallery versus something related to the theme? We’d be happy to take a look at it if we can reproduce the issue at hand.

Thanks!

– Cais.

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.

@puregraphx – Here is the conditional that needs to be met for that specific text notice to be written:

if (defined('W3TC') && defined('WP_DEBUG') && WP_DEBUG && !is_admin()) { ... }

I would suggest looking at the W3TC usage and/or wether WP_DEBUG is set to true as possible sticking points.

– Cais.

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.

@puregraphx – Are you using the Avada theme on those other sites; or, similar configurations of the theme?

– Cais.

Unfortunately we are using NextGEN only on this 1 site.

@puregraphx – We do not have any specific Avada error checking although it does appear their template methods are triggering the problem all the same.

As is, there may not be much we can offer as the Avada theme tends to intermittently have issues from one version to the next. I would suggest contacting their support to see if they have any thoughts on why their templates are triggering this issue.

Otherwise, you could set DEBUG to false…

Thanks!

– Cais.

Ok, we will contact their support

@puregraphx – Thanks!

– Cais.

Hi @imagely,

We heard back from the Theme Fusion Support theme and they confirm that in the Avada theme, the wp_footer() is called on every page. As it outputs a fair number of JS files, this missing function would be noticed right away.

They are open for direct contact with you to sort out if this is just incorrect reporting to the log file or if there is some other issue why his plugin is not detecting if wp_footer() function is called or not properly.

@puregraphx – Thanks, again!

– Cais.