Fix WordPress upgrade error: No Update Required -Your WordPress database is already up-to-date!
I recently upgraded my blog to WordPress 3.x and everything seemed to go smoothly with the process. But after upgraded when I go to the WordPress admin, I still get the upgrade page, and message show like:
No Upgrade Required
Your WordPress database is already up-to-date!
When I clicking the “Continue” button it sent into a loop.
After much troubleshooting, the solution for fix the “No Update Required –Your WordPress database is already up-to-date!” looping. I have re-upload all files & folders except the wp-content folder from a fresh download of WordPress.
Incoming search terms: no update required your wordpress database is already up-to-date!, je wordpress-database is al up-to-date, wordpress database update required loop, No terms in your WordPress database, no update required, wordpress database update required, wordpress move No Update Required
Related posts:
- Solve wordPress asking FTP account while trying to install, update One of the great features of WordPress is that it allows you to automatically install and upgrade themes, plugins and upgrade WordPress version. But this features is fully support on...
- Fix “Briefly unavailable for scheduled maintenance. Check back in a minute.” The core automatic upgrade feature in worddpress was added with version 2.7. During the automatic upgrade WordPress the vistors will see the “Briefly unavailable for scheduled maintenance. Check back in...
- Fix iTunes “Network Connection Timed Out” error when downloading iPhone update Some users have problems with “Network Connection Timed Out” error when trying to update their iPhone, iPad, or iPod touch to a newer version of iOS from iTunes before the...
- Page views counter to WordPress posts and pages If you need to have page views count on your wordpress blog for your posts and pages. We has a plugin for your needs which it work very well for...
- How to add Google +1 button to wordpress Theme The Google +1 is hottest social app by Google and many people are really getting serious about the Google +1 is because it will be used as one of the...
I just came across this after an update – traced it to the memcache object cache plugin. The update does not clear its own cached objects.
I have numerous live sites on my server, so restarting memcached is not an option, as users would be forced to log in again.
I just changed the cache keys so that new objects would be cached under a different name – the old ones will expire or disappear at next kernel update when I reboot the servers.
Alternatively, just rename wp-content/object-cache.php temporarily to continue admin.
I have a suggestion for the author of wp-content/object-cache.php, DB_NAME needs adding to the key, otherwise the caches of users using “wp_” prefix on different databases will clash.
I had the same problem. I rename the object-cache.php and the site works fine. Later i discover that the W3 Total Cache plugin was the problem. I delet it and my site still work fine.