WordPress - PHP Warning failed to open stream: No such file or directory (advanced-cache.php)

Question

I'm getting this PHP Warning on back-end and front-end pages (WordPress) and can't figure out how to fix it:

Warning: include(/home/.../public_html/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /home/.../public_html/wp-settings.php on line 84

Warning: include(): Failed opening '/home/.../public_html/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/.../public_html/wp-settings.php on line 84

Indeed, there is no advanced-cache.php in that directory (not sure if ever was), but absolutely the same configuration works on a different server without warnings.

Will appreciate any help. Thanks.

Solution 1

I think you have installed Advance cache plugin, and a setting WP_CACHE

define('WP_CACHE', true);
// or may be it is a file like, if so then comment this line,
// below is the statement which need to be commented
// define('WP_CACHE', is_file(__DIR__.'/wp-content/advanced-cache.php'));

to prevent this error you can set to false, like

define('WP_CACHE', false);

Solution 2

../wp-content/advanced-cache.php is generated dynamically when any caching plugin gets installed, especially caching plugins from wordpress.org use that. So you will not be able to find that file on fresh WP installation.

Please refer link

In your case, I assume that you have installed some caching plugin and due to any reason advanced-cache.php file is deleted from folder or there may be permission issue for executing the file. That's why when your caching plugin tries to search and include advanced-cache.php file than it cannot find it or execute it and this throws the error you mentioned.

For further possibilities and suggestions, I need to know which caching plugin do you use. Let me know if you want me to help further...

Comments

[elkah]

Thank you, it helped. It was WP Super Cache and I did have define('WP_CACHE', false) in config.

[elkah]

It's WP Super Cache. I solved the issue disabling define('WP_CACHE', false);. Thank you in any case.

[Tim Van Dijck]

"If your car makes a funny noise, don't use it"