faceless105

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.

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.

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

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

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

i just wanted to bump this to see if I could get any help. I exported the databases and imported them into a new database and changed the refferences in the wp-config.php file but now when people log into my blogs they get a problem with insuffecient permissions. which I dont understand, obviously the db is in tact since everything looks normal from the outside, I think the problem is coming form the database but i’m not sure where since i’ve checked them and they match up perfectly to the origionals, so any help would be pretty much amazing.

i ended up keeping the site but relocating the database. I followed the sintructions to point the files to a new database with the dbname, login, pass and the correct prefixes but when users tried logging in they could see the first page but when they did anything else it would tell them they did not have suffecient permissions. what are some possible causes for this?