include(…/wp-content/advanced-cache.php): Failed to open stream: No such file or directory
“advanced-cache.php: Failed to open stream” in WordPress: causes and what to check
# Common log entries
PHP Warning: include(…/wp-content/advanced-cache.php): Failed to open stream: No such file or directory in …/wp-settings.php on line …
When WP_CACHE is set to true, WordPress loads wp-content/advanced-cache.php before anything else. If the file is missing or belongs to a removed caching plugin, PHP prints this warning or the page stops.
Which of these matches what you see?
The plugin removed its file and the setting stayed, so WordPress looks for a file that no longer exists.
Each caching plugin writes its own advanced-cache.php. Switching plugins can leave a file that loads code from the old one.
The file stores absolute paths from the old host, so its includes fail on the new one.
Common causes
References
What the system does
Errors caused by stale cache files or a lost object-cache backend are handled automatically: the system removes the stuck cache files and, when the cache backend is unreachable, removes the leftover configuration. Fixes are made on a copy of your site in the recovery station and written back only after re-verification passes. In your site’s database, the protected tables (members, comments, orders and form submissions) are copied as structure only. In SSH and FTP mode, the system creates a pre-recovery backup on your host before writing back and restores from it if verification after write-back fails. If the recovery cannot be completed, the recovery fee is refunded in full.
- Initial assessment: Enter the site URL
- Copy to the recovery station: Work runs on the copy
- Find the cause: Item-by-item checks
- Recover and re-check: Home and inner pages
- Write back or deliver: Only after re-checks pass
Use WP119 when the warning blocks pages and you prefer not to change files in wp-content.
Assess my site →