Noticed a few people mentioning this, but not seeing ill-effects either. I don’t have a conclusive answer but hopefully someone will soon…
What I did was go to http://mysite/wp-admin/upgrade.php
You get the prompt there.
Thanks both. I tried pizzaman’s suggestion and it seemed to upgrade the DB ok. 🙂
Matt
I guess I should look at upgrade.php before stating this, but I’m pretty sure it is smart enough to not do anything if nothing needs to be done. In other words, can’t hurt to hit it (but I don’t think it is necessary for the 2.0.3 to 2.0.4 but am willing to be wrong).
I think you’re right, Handy.
Yeah, I didn’t get the prompt either, but that is all cool. I just mnaually type in the upgrade link.
I followed the uplead steps but was not was not “prompted to click on the link to upgrade your database.” But worse – the only thing that shows up now on my browser is the directory of file names and not the graphical home page. (Although, I did get the graphical dashboard by selecting [mysite]/wp-admin/.)
What is wrong? Also, what am I suposed to do to upgrade.php?
One more thing: question marks appear over the name of each directory of the server as appears in the remote treeview of Filezilla.
Oops. Fuggitaboutit. (Didn’t have index.php in root directory.) Am going to forget about lack of prompt.
The codex article was wrong regarding the need for a database upgrade between v2.0.3 and 2.0.4 – I have updated it now.
There were no changes in the database schema between v2.0.3 and v2.0.4 so no need to worry about running upgrade.php this time.
