Absolute path in WPCACHE home fails but relative path works
-
Hello,
I am using WP 4.1.1 and Super Cache 1.4.4
I have set all configs properly (I know it is “properly” because I have done it a gazillion times in other sites and they work perfectly) and the lines of code are OK in WP-CONFIG and HTACCESS.
The plugin IS generating the cached files, I can see them physically via FTP.
However, each time a page loads, it regenerates the cache. I switched on Debugging and it says something among the lines of “No such file found, generating the cache again”
So in essence, each time I reload the page, it re-caches it.
After spending 27 years, I somehow noticed that if I change the WPCACHEHOME to a relative path, it works perfectly. However, the backend throws a gazillion errors and fixes it. So, either it works for the backend or it works caching, but not both.
In other words, the default code is:
define( 'WPCACHEHOME', '/home/public_html/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager
… this fails to use cached files.
however, this:
define( 'WPCACHEHOME', '/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager
… caches everything nicely but the backend panics and reverts it.
Any idea??
- The topic ‘Absolute path in WPCACHE home fails but relative path works’ is closed to new replies.