[oceania]

ok 3 years ago i had a partner in the station
she handled wordpress blogging
she set up several sub-domains that all used the same db
tonight i tried to upgrade one of the subdomains with the current version fo WP
the one that it had went back maybe 2 years
so ancient that WP had to upgraded manually
anyway
did what i was suppose to
but when i went to the admin section i was diverted to the main subdomian blog
so the question is
how do i get out of this mess
update the blog
maybe even unravel the domains so that they have separate db

sigh
pass the red
hugs

[gonzogone]

so are these subdomains running independent copies of WP, but all pointing to the same DB? I'm assuming that's the case...

I'm guessing the real issue right now is that by upgrading one WP, it updated the database with some new information that the other copies don't understand... Most likely, you'd be fine to do upgrades on the other WP copies, even though they are pointing to the same DB. VERY good to do a backup first of the DB.

To get them all on their own DBs, will be some work at this point. You'll need copies of the original DB for each one to point at so you don't lose any information. From there, you'll need to edit the config files to reflect the database changes. It's going to be a blast...

Before you even think about getting started with this... verify what really happened... that you really do have more than one WP install pointing to a single DB.

I'd bet GSM will have some input on this, he's always found fun ways to work with WP, so may have some direct experience with how to get back to a stable point.

[Tigger]

please tell me you also hit the back up tit before starting this

[gonzogone]

yeah... I did rather make that assumption... but...

[oceania]

good morning
thanks for jumping right in
unraveling the db so each blog (subdomain) has its own db isnt as important as understanding what i have...

which is something S4E touched on in his workshop
sometimes you get someone to work on a project and they go away
and you are left to fix or start over

so here i am

i have 5 subdomains for blogs
originally set up for hosts to use to blog about their shows
only 1 ever used it religiously
Sascha who you know from the boards

after Kevin G's workshop
i got a task list to upgrade it

yes i backed it up
but i didnt know about a TIT button (hmmm must be a AF247 specific function)
LOL

so i went to sascha.radiodentata.com
and manually added the new WP files
making sure i used the db username and passwords in the current config file that was in his directory

after it uploaded i typed in sascha.radiodentata.com
a screen poped up that said
something about having the lates WP
and then redirected me to the defunct subdomain
radio.radiodentata.com
which originally was suppose to be feed the latest blog posts from the host blogs (on the other subdomains)
ok i think it's time for Tigger to pass me a glass of wine

i checked the config file on that directory and it had the same db
so i checked the other subdomains and yep same db information

so yes each have a copy of WP on them
so do i have to upgrade all the subdomains....?
gladly hire someone to figure this out and then explain it to me
but looks like more of a lesson of hard knocks

anyway
instead of balancing checkbook (another real joy)
i reinstalled the backup and sascha is back up

so any suggestions for step one
getting a more current version of WP for his blog

step 2 -since the other subdomains maybe have 2-3 post on them and are essentially dead -
can i remove them without affecting the db?

thanks to all that look
special thanks to those that can comment without laughing
LOL

[Gaystoryman]

From the sounds of it, you have upgraded from a version to a new one, that has changed hooks, and db tables. Depends on what version you were originally running, and which you upgraded to.

You may also want to check your htaccess file, and the permalink structure once you do a fresh install of WP.

Running several installs off of one DB is not usually a headache, if you maintain a good update schedule. So I'd also check the config files in each sub domain, find out what the WP prefix is set to, for each sub domain. It should be different for each one, if not, then more than likely you will need to upgrade all sub domains in order to have them all point properly.

Also, not just backup the db, but backup your WP-Content folder in each sub domain, mainly the THEME files, as this is where your custom changes to any themes will be located. An upgrade will erase them.

I'd also do a backup of your upload folder, PLUS I would go into admin > tools and do an EXPORT of WP that you save to your HDD. This will give you a good post/image backup in an XML file that you can easily IMPORT into a new install, including authors.

Should note, that an upgrade from 2.9 to 3.0 DOES change tables as does an upgrade from 2.8 to 2.9 etc.

A work around is to take your old wordpress, and upgrade step by step to the newest version. In other words, if you are running 2.5 then upgrade to 2.6 then to 2.7 then to 2.8 etc. After each install/upgrade, you should be prompted to upgrade the db. [You have to access your admin all over after each upgrade, for the prompt to show.] Eventually you'll have it all current, with any db changes being properly altered, by wordpress itself, instead of you having to go into your db and do it.

hth

[oceania]

the work around sounds like something i could handle -
thanks so much for taking the time GSM

[SaschaIllyvich]

Thank you all, and yes I am the You Know Who with NO affectation for bananas LOL!

S