Beware of CACHE (especially for mirror versions)

  • WP 2 now includes caching, which could cause you major hassles if you try and move/download the site to a new location.

    The cache causes issues with logging in, redirects, and even may show incorrect information on your options page (it could be the cached version of the old site, and now what is actually in your db).

    So to avoid any hassles, simply delete the contents of the cache folder in wp-content.

    I wonder if making changes directly to the db will now not be seen under options due to caching?

Viewing 1 replies (of 1 total)

  • Thanks so much for posting this. I’ve been having problems with my local copy of WordPress since upgrading and I couldn’t figure out why. I’d manually change the URIs in phpmyadmin and I couldn’t understand why the page would be partially called but also point to the live site. This solves it. I didn’t realise the cache was still looking for the old site. It does prevent database changes from being recognised for some time, and definitely messes with logins and redirects. I’ve just recently switched web hosts and now that I know this I’ll be sure to delete the cache before trying to update my information.

Viewing 1 replies (of 1 total)
  • The topic ‘Beware of CACHE (especially for mirror versions)’ is closed to new replies.