• Resolved BinkyM

    (@binkym)


    It’s me again:

    I’m helping a man who had several WP 2.0.2 blog get updated to 2.3.3. Copied one down off his server so I’d have a backup, then put it back up there again with a new name, leaving the old one in situ in the event of a disaster, and sure enough, I’ve got a disaster! (Years of learning have taught me to be prepared!) I ran the updater, or tried to, but I got the dreaded:

    We were able to connect to the database server (which means your username and password is okay) but not able to select the example_com_-_wordpress2_v1U2I47o database.

    Are you sure it exists?
    Does the user example have permission to use the example_com_-_wordpress2_v1U2I47o database?
    On some systems the name of your database is prefixed with your username, so it would be like username_wordpress. Could that be the problem?

    I’d been tempted to go in to tear down and recreate his database, but now here’s the thing: the old 2.0.2 blog I left in place is using the same database, and has the same info in the config file, so that seems not to be the problem. I even copied the config file over from the 2.0.2 blog just in case I’d made a copy/paste error, but I continue to get the same danged error. This is making no sense to me. Is this ringing any bells with anyone?

    Binky

Viewing 5 replies - 1 through 5 (of 5 total)
  • Well, do keep in mind that the blog URLs are stored in the database, so if you’ve moved the files but not yet told the db about it you’re going to have all sorts of entertainment… 😉

    Thread Starter BinkyM

    (@binkym)

    HandySolo:

    They are? I had no idea. Hold on a sec; gonna go rename the directories. Naw; that didn’t help. The new 2.3.3 blog now is in a directory with the same name as the old 2.0.2 blog, and WP is still grumbling about the same nonsense. Is there something else I’ve missed? Maybe some permissions that haven’t been set yet because the upater’s been farting around with this dumb directory-naming nonsense?

    Binky

    example_com_-_wordpress2_v1U2I47o database

    Whoops, I should’ve asked this first:

    Is that really the prefix being used in the database? What’s specified in your config vs. what’s the actual prefix being used in the database?

    Thread Starter BinkyM

    (@binkym)

    HandySolo:

    I’m sorry; there was a miscommunication here. Unbeknownst to me, the database had been deleted, and the blog I *thought* I was looking at was using a different database, but I was looking at another config file for a defunct blog which *also* referenced the same deleted database. User head gap. I’ll smack myself in the head with a hammer for you.

    Binky

    Ah ha! A /face-palm moment indeed. 🙂

    Well, glad you got that all figured out.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Duplicate blogs: one can’t connect to database’ is closed to new replies.