Is your wp-config.php writeable by the webserver? I think this is happening because you cloned your site, and paths differ.
Open up wp-config.php and check “WPCACHEHOME”. Is the path to the wp-super-cache directory correct for your staging server?
Hi @donncha
thanks for your reply.
I have no idea. I rarely if ever, go to the backend of my website and wouldn’t know where to look for wp-config.php let alone find out if it is writable on the server or to ascertain if the path to the wp-super-cache directory is correct. I am not a developer.
The logic however dictates that you may be looking at the wrong issue. The plugin which was broken has already fixed itself. There is no need to re-write anything. It’s done. It’s working (I hope).
The only remaining issue is a nuisance persistent notification about this development which doesn’t go away after reloading – which it says it will.
Screenshot.
Could you give me a fix that doesn’t require rewriting any files or checks at the backend.
if not- I will leave it. It’s only a staging site.
thanks
That’s what I’m talking about too. When you cloned your site the WPCACHEHOME was incorrectly set, possibly. That’s why I asked you to do those things.
I think the simplest way to fix it is by uninstalling WP Super Cache from your site and then installing it again. That will set it up with the right settings for your particular site.
yes, this is the simplest solution. However, when I opened Admin this morning – that notification was gone. I deactivated the plugin and activated again, just in case. Didn’t have to uninstall.
all good.
thanks!
Hi @alathea9,
I’m glad our very own Donncha was able to help 🙂
If you’re finding WP Super Cache valuable (as well as our support) please consider leaving us a review. No pressure of course 🙂
This thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!
