rsgrone

why don’t you check your error logs (php) or ask your host to check them for you.. the php error log will tell you everything you always wanted to know about what is going on with your wordpress blog…

I am running MySQL 5.1.50 on one port and 5.1.11 on a different port and really haven’t seen anything that would indicate any issues other than what has been stated above regarding plugins… alot of the plugins still through depreciated code errors in the php logs…

FYI, on mySQL 5.0 the old query would take around 3-5seconds compared with 180sec on mySQL 5.1. YMMV

I do not understand this statement….

Looking back at your original post… you state that you set the site up as a “sub-domain” and now moving it to a new domain? Is the new domain, a “sub-domain”?

If it is not then, you still have work to do on the DB….

When you say sub-domain do you mean first.first.com or first.com/first ?

And finally, without having access to what you are doing… is one site using “multi-site” and the other not or vice versa? And what was your original permalink settings?

If all else fails, I would try setting the permalinks to defaults, dump the DB again, and start a fresh…

Good Luck…

What are you using to do the DB move? MyPHPAdmin or MySQL Tools/Workbench? The Workbench will do the migration for you, just plugin the new prefixes etc and bada bing…

If you are using MyPHPAdmin, then you will have to go into the imported daabase, and manually change prefixes, etc…

What’s the url to your new site? What’s the “new” prefix that they are forcing you to use? If you have that information, and would link to zip the .sql file, I can see if I can work-up the fix for you…

Do a find and replace using your orignal site name (search for http://http://www.first.com and replace with http://http://www.second.com)

Disregard that… do a search for www.first.com and replace with www.second.com (ignore the http as, it will replace all instances referring to your original domain name…

Listen I cannot get this thing to post a url with it throwing the http in front of it… do a search and replace with the old site name and replace with new site (domain name) WITHOUT the HTTP://

Wait a minute… you transferred a WordPress database from one domain to another domain? You cannot do that…

How did you transfer the files? Did you use WordPress Import/Export or did you move the database?

If you moved the database, it still has the old hostname in it and it will never work if the original site is now “down”…

In other words, you can’t take the database from your-original-site.com and simply use it in your-new-site.com as the sitemeta is set-up for the first domain…

You have a lot of work (well not really) to do on the original database… you need to modify the wp-options table, the sitemeta table just to name two…

That is why I asked you to do a dnslookup…

Does this make sense to you?

What type of access do you have with your database? Sounds like the wp-comments is corrupt…

I have seen this before and manually rebuilt for a customer (it was a lengthy procedure) however, if you have access to say, MyPHPAdmin you may be able to use their built-in functions to automatically repair the table (wp-comments) other than that, if you have a recent back-up of your database you can restore (I backup all my DB’s daily)…

There is a plugin called Delete Revisions that has a built in Database optimization/repair tool in it… you can give that a try otherwise, you will definitely need access to your database to do so..