Upgrade misdirection…
-
Background — for several years I have had 2 WP blogs on my hosted domain. Each has it’s own parked (sub-)domain which points to a unique directory on my main domain. For the better part of the past year, I have been inactive on both blogs. Recently I decided to update both to version 2.9.3.
The first blog (“PJ” for short) auto upgraded and it worked like a champ. I spent a day or two changing themes and getting everything the way I wanted it then I decided to update the second blog (“AA” for short).
“AA” did not auto update, so being a WP veteran, I manually extracted the files and uploaded them to my web host using FileZilla. Now, I can’t login to “AA”. When I manually entered aa.com/wp-admin/wp-login.php, it takes me to a WP Login with “Return to “PJ” ” at the top.
Now, being a self-proclaimed veteran, I took it upon myself to look at my MySQL database and I see in the 1 database, 2 sets of WP files. The “PJ” site uses the normal wp_ prefix and the “AA” site uses the “AA_wp_” prefix. When I look at the 2 “_user” tables I see a different structure in each… I seemingly can’t force “AA” to update my aa_wp_ database b/c it says everything looks fine.
Two of my main concerns are user authentication key changes have been made since my “old” version of WP and the wp_config.php file has some updates too.
Any suggestions?
TIA
gpence
The topic ‘Upgrade misdirection…’ is closed to new replies.