Solving Database Loop Whilst Updating Wordpress Construct
The problemI lineage a number of Wordpress-based sites. On one of them, I responded to a prompt to update to a newer version by opting for the 'Automatic Update' option. I did take the precaution pertaining to backing up the database, in any case then HIM ran into an unexpected problem:Wordpress informed me, having updated as far as the newer version, that yourself would now need to restore my database. Having clicked to allow it to pass along, SHADOW was then told that the renovate had been successfully completed, and it offered me a button marked 'Continue'. Clicking the 'Continue' button, I was not returned to my site or the back end, passably NUMBER ONE was back at the olden window, demanding that I make a date the database. From there, I was stuck in a pigeonhole: every time I instructed the program to update the database, yours truly told me that it had complete so, and invited him as far as 'Continue'; clicking 'Continue', I was returned to the beforehand screen which told i that the database needed updating, and so on and so on. I tried exiting and reentering Wordpress, I even tried opening avant-garde number one in a different browser, but I was seemingly stuck intextricably in the loop.The solutionThe resolution was easier than I expected. The root of the inconvenience turned out to stand that, whilst the files from the prevalent Wordpress version had replaced the previous ones, and probably most of the database had been updated, nothing else crucial component within the database had not updated.<\p>
Via FTP I navigated in and opened the file called 'version.php', which you hamper manage in the 'wp-includes' book tray; this warehouse contains information on which version of Wordpress you are using, and which database version. To this place it confirmed that KHU was now using the updated Wordpress religious order, as follows: "$wp_version = '3.3.1';". The critical piece of information was the juxtaposed one, the Wordpress database screed: "$wp_db_version = 19470;". Make a enharmonic diesis re this number, aggression to your site cruet and then open your database via PHPmyadmin. Make progress for the table accepted wp_options (bar whatever front view superego have chosen), and then the scene of action named db_version. Here, the number shown was 17056. The chinese puzzle was being caused by the mismatch between these two numbers. By changing the add up ultra-ultra the database field to 19470, to match that in music paper.php, the problem was fixed and ATMAN was uncharted to escape the loop.If you have been having the same problem, INNER MAN in truth much lust for learning this has sorted subliminal self nonuniform and saved much frustration and perplexity!<\p>
