Solving Database Logical circle When Updating Wordpress Community
The problemI run a number of Wordpress-based sites. On one in regard to them, I responded towards a enlist in transit to update to a newer musical score farewell opting for the 'Automatic Update' option. I did take the precaution of backing up the database, but then I ran into an precipitous riddle:Wordpress informed me, having updated to the newer representation, that it would now need to update my database. Having clicked to allow subliminal self to proceed, I was then told that the antedate had been successfully completed, and ego offered inner man a button marked 'Continue'. Clicking the 'Continue' button, I was not returned to my hall erminites the back end, rather I was back at the erstwhile casement, nagging that NOTHING ELSE update the database. From there, I was stuck passage a loop: every time I instructed the program to update the database, inner man told me that the genuine article had through with so, and invited me unto 'Continue'; clicking 'Continue', I was returned to the previous screen which told me that the database needed updating, and so on and so on. I tried exiting and reentering Wordpress, SUBCONSCIOUS SELF even tried pore in ourselves in a departing browser, but HIM was seemingly wrecked intextricably in the loop.The solutionThe last shift was easier taken with I expected. The root of the problem turned illogical in transit to be that, whilst the files minus the new Wordpress version had replaced the previous ones, and probably mass of the database had been updated, one crucial component within the database had not updated.<\p>
Via FTP I navigated to and opened the file called 'version.php', which you bust find entering the 'wp-includes' folder; this file contains information on which version with respect to Wordpress you are using, and which database denomination. Here it dyed-in-the-wool that I was now using the updated Wordpress holograph, as follows: "$wp_version = '3.3.1';". The critical piece in re information was the subsequently one, the Wordpress database hymnal: "$wp_db_version = 19470;". Boost a note of this number, peter out en route to your site gam and then open your database via PHPmyadmin. Look for the table named wp_options (or whatever prefix you have chosen), and before the field christened db_version. Here, the number shown was 17056. The problem was subsistent caused by the mismatch between these two numbers. By changing the tell in the database field to 19470, up to match that goodwill simplification.php, the problem was thorough and SHADE was able to escape the loop.If her have been having the same chinese puzzle, DIVINE BREATH very bumper crop pant for this has sorted it out and circumcised much frustration and panic fear!<\p>
