Wp-Cache-Config.Php Is Missing. Please Reload The Page
Support » Plugin: WP Super Cache » Unable to deactivate plugin
Unable to deactivate plugin
I’m unable to edit the setting or deactivate the plugin.
When trying to deactivate:
Could not remove WPCACHEHOME define from /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-config.php. Please edit that file and remove the line containing the text ‘WPCACHEHOME’. Then refresh this page.
When trying to edit settings:
Error: Configuration file /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content/wp-cache-config.php s missing. Please reload the page.
Warning! Could not update /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-config.php! WPCACHEHOME must be set in config file.
Warning! /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content/advanced-cache.php does not exist or cannot be updated.
If it already exists, please delete the file first.
Make /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content writable using the chmod command through your ftp or server software. (chmod 777 /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)
Refresh this page to update /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content/advanced-cache.php
If that doesn’t work, make sure the file /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content/advanced-cache.php doesn’t exist:
Open /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content/plugins/wp-super-cache/advanced-cache.php in a text editor.
Change the text CACHEHOME to /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content/plugins/wp-super-cache/
Save the file and copy it to /home/hp3-linc5-nfs2-y/619/1210619/user/htdocs/wp-content/advanced-cache.php and refresh this page.
I recently migrated this site to a new server using duplicator plugin. Not sure if this has anything to do with the errors but worth pointing out.
Thanks in advance.
The page I need help with: [log in to see the link]
Wp-cache-config.php is missing. please reload the page
This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.
The static html files will be served to the vast majority of your users:
Users who are not logged in.
Users who have not left a comment on your blog.
Or users who have not viewed a password protected post.
99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.
The plugin serves cached files in 3 ways (ranked by speed):
Expert. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file which is risky and may take down your site if modified incorrectly.
Simple. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. It’s easier to configure as the .htaccess file doesn’t need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode.
WP-Cache caching. This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. Set the constant “DISABLE_SUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching.
If you’re not comfortable with editing PHP files then use simple mode. It’s easy to set up and very fast.
Don’t cache pages for known users.
Extra homepage checks.
Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds.
Consider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you.
Preload as many posts as you can and enable “Preload Mode”. Garbage collection of old cached files will be disabled. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.
Even with preload mode enabled cached files will still be deleted when posts are modified or comments made.
Active development of this plugin is handled on GitHub.
Translation of the plugin into different languages is on the translation page.
If you need more information than the following, you can have a look at the Developer documentation.
You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.
To make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling “Preload Mode” in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.
Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:
1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.
2. Scheduler. Setup how often garbage collection should be done.
3. Notification emails. You can be informed on garbage collection job progress.
There’s no right or wrong settings for garbage collection. It depends on your own site.
If your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.
If your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.
The cache directory, usually wp-content/cache/ is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.
OSSDL CDN off-linker has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support origin pull. This means the CDN will download the file automatically from your server when it’s first requested, and will continue to serve it for a configurable length of time before downloading it again from your server.
Configure this on the “CDN” tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.
There are now REST API endpoints for accessing the settings of this plugin. You’ll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the “rest” directory.
It is now possible to hook into the caching process using the add_cacheaction() function.
Three hooks are available:
‘wp_cache_get_cookies_values’ – modify the key used by WP Cache.
‘add_cacheaction’ – runs in phase2. Allows a plugin to add WordPress hooks.
‘cache_admin_page’ – runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.
There is one regular WordPress filter too. Use the “do_createsupercache” filter
to customize the checks made before caching. The filter accepts one parameter.
The output of WP-Cache’s wp_cache_get_cookies_values() function.
See plugins/searchengine.php as an example I use for my No Adverts for Friends plugin.
If things don’t work when you installed the plugin here are a few things to check: