starting to lose hope

quick bump…

I was wondering if anyone could help, i’ve found that the problem occurs when I have the table prefix set to anything other then wp_, even though i know to specify the new prefix in the wp-config.php

the wp version is 2.0.5 if that helps. this has become a pretty big problem since i can’t find a work around for it. any help you guys can give would be great.

thanks

This might not be the solution you were hoping for, but if all else fails and you are desperate, maybe you could try something like the following:

1) Back up all of your installs (directories and databases)

2) Reinstall fresh copies (however many you need) all to one db keeping in mind the different prefixes you need to make.

3) Copy each individual backup and paste them into their newly installed folder overwriting everything.

4) Transfer the old db info into the new relevant tables.

Again this is probably a last ditch effort and you should wait for someone else to make a more intelligent response.

thats almost what is causing the problems sadly, lol. seems that when i have a prefix to the tables other then wp_ then i lose all my admin abilities

i don’t mean to sound rude about this but aren’t there any staff that’ve read this?

What’s a “staff”? You mean the unpaid volunteers? Yes, we’re here.

And to head off the next question: no, moderator does != expert on every little facet.

I host many blogs out of one db. I’ve never observed the problem you’re having. As long as each blog’s config has a different prefix, it shouldn’t matter.

Installing_Multiple_Blogs

I’m going to assume (lack of data above) that each blog that was in its own database had the wp_ prefix. So, when you try to restore it into a new db, each one is trying to restore on the same set of tables (starting with wp_). That sound about right?

If so, you’ll want to edit each db’s backup. Find the create table and insert statements and edit the wp_ to the new/correct prefix (that matches what’s in your wp-config file).

i don’t mean to sound rude about this but aren’t there any staff that’ve read this?

WordPress is not a company. They don’t have staff. This is open source software, made for free, given away for free, by volunteers. If you want paid support, you should a) look at the wp-pro mailing list and b) expect to pay for it.

sorry for the comment above it’s just getting kind of frustrating, i’ve been digging through code for the last few days and analyzing the databases to try and find the problem without any luck yet.

i’ll try to give as much detail as I can…

i think it’s pretty clear now that all the blogs were one seperate databases. what i did was through phpmyadmin, I exported the databases then imported them into a master database. as I exported them i renamed each set of tables to have a unique prefix since if I kept wp_ then i’d have problems. then I went into the wp-config.php file and updated the database name, user, pass, and matched up the prefix names, but it’s been without any luck.

It’s very strange though, from the outside, before you log in, the blog looks fine, all the posts load up just fine, but once you login it accepts the login info but none of the admin options show up on the dashboard, and if you hit any of the links then it gives you a message about nothing have the propper permissions.

the database user account has all priviledges allowed so that isn’t the problem (which seemed most likely to me).

The weird thing is, if I change the tables back to the wp_ prefix, even though they’re in the new database, and change the prefix in the wp-config.php file then everything works perfectly. seeing this happen it leads me to think there is a bug in the code and somewhere there is a select statement calling wp_ instead of the defined prefix, but i haven’t be able to find it and i think i’ve gone though all the select statements in the site so far, thus the frustration.

I’ve also wondered if my method of exporting the databases was the problem but since they loaded fine on the new database with the old wp_ prefix i can see everything is perfectly intact. sadly i can only do this for one blog at a time so keeping the old prefix isn’t an option.

So i’m just about 99% sure that it’s a very small bug that is causing all these troubles but i so far haven’t been able to find out what it is ??

honestly, any help i can get is incredibly appreciated.

Dump the data for your tables, and then search the data itself for a “wp_” anywhere. I’m thinking that maybe the table prefix is stored in the database somewhere. Unlikely, but possible.

Otto42
you got it right on. I found two tables with the words wp_ in them, the usermeta and options. I changed the refferences in the usermeta table from wp_ to the new prefix and that has seemed to fix it. I’m not sure what the options table refferences yet but i’m just waiting to see if changing that one as well generates any errors.

Okay, so apparently a ton of people were having this issue but it wasn’t anything like my problem, except for faceless105. I had some trouble, but I eventually got it to work.

My advice to anyone else having this problem: make sure that when you’re replacing wp_ with whatever_ that you make sure you DO NOT replace ALL instances. Remember, you’re just changing the table names and a couple links to those tables in your data. Do not, for example, replace instances of _wp_ with the leading underscore. Definitely make sure you change the information in the usermeta table.

I hope this helps someone from doing something rash.