• Hi,

    Good day.

    I got this error on the backend. This error occurs after updating the theme to the latest version.

    Warning! Could not update /home/domain/public_html/wp-config.php! WPCACHEHOME must be set in config file.
    Warning! /home/domain/public_html/wp-content/advanced-cache.php does not exist or cannot be updated.

    I tried to solve the issue using the instructions on the plugin page but no good On option number 2, I can find the word Cachehome on the advanced-cache.php. Do you have a video tutorial for this so I can check it myself? or any recommendations to solve the issue. Thanks

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • You need to edit your wp-config.php and add a line like this:

    define( ‘WPCACHEHOME’, ‘/XXXXXXXXXX/wp-content/plugins/wp-super-cache/’ );

    where XXXXXXXXXX is the path to your wp-super-cache directory.

    That error message is wrong and has been fixed in the Github code repository for the next release. Sorry for the confusion!

    Thread Starter Toink22

    (@toink22)

    Hi @donncha

    Thanks for replying. I opened the wp-config.php and define( ‘WPCACHEHOME’, ‘/XXXXXXXXXX/wp-content/plugins/wp-super-cache/’ ); is already on it. ??

    What should be the best option for me to fix this issue? Thanks

    Is it above this line in wp-config.php ?

    require_once(ABSPATH . 'wp-settings.php');

    Hello!

    I have the exact same issue (it appears) as the above.
    In my case: yes, it is above the line:

    require_once(ABSPATH . ‘wp-settings.php’);

    Not just above it, but in the middle of the file:

    define(‘WP_CACHE’, true); //Added by WP-Cache Manager
    define( ‘WPCACHEHOME’, ‘/home/xxxxxxxx/domains/xxxxxxxxxx/public_html/wp-content/plugins/wp-super-cache/’ );
    define(‘DB_NAME’, ‘xxxxxxxx’);

    What should I do to fix it?

    Best,
    Theodoor

    @rotsmedia Is your wp-config.php writeable? I think the logic in the function that creates advanced-cache.php is a bit broken as it mixes up checking if the plugin can write to the config file even if it doesn’t need to. I’ll be releasing a new version shortly that fixes it.

    Hello Donncha,

    Thanks for your quick reply.
    Yes wp-config.php is writeble. I changed this when trying to fix it.
    Oke so after the next release and update the problem should be solved?
    Great, i’ll wait for that.
    Thanks

    OK, if your wp-config.php was writable then it was another bug in a related piece of code maybe, which is fixed too. ??

    @rotsmedia Can you give the development version a go? It will almost certainly be the final version that I release tomorrow but it would be good to get feedback that it fixed the issue with this warning.

    Grab it from this page that has all the info:
    https://ocaoimh.ie/y/2o

    Hi,
    I’m reading that it might cause problems or crash the site. I’m not comfortable doing that since I’m actually trying to help someone with their site, so it’s not actually mine. I will try the next update when it’s available. Hope it works out.
    thank you.

    The new release yesterday is the same code, so that will fix the WPCACHEHOME problem once you upgrade. ??

    Thank You !

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘WPCACHEHOME must be set in config file.’ is closed to new replies.