knagles

Ok i fixed it.

The SQLDatabase is not being hosted on my server its still on the old one. That is why repairing it would not work.

Why its still on the old server i dont know but now i should be able to move it ok.

Thanks for all your help

Kyle
??

What kind of backup are you talking about? Database or theme? A database backup is only as good as the time it was made. If your databse backup is 6 months old, than you’ve lost the last six months of content. Don’t depend on a client to do their own backup.

Turns out the backup we have(mysql database) is from sunday. So this backup will have the same issue in it. So forget about restoring the backup, lets see if we can fix it.

You’re confusing the three critical aspects of WordPress: design, administration and content. 1) Design is the theme. You back that up and update that differently than the content, which is the database. Copy the theme via FTP to backup. 2) Administration is WordPress itself. Updating WordPress may impact your theme (i.e., new functions that are available in WP3) but isn’t necessarily going to repair a database. It can’t do everything that say, phpmyadmin can do. 3) Content are posts and pages, etc., and are in the database. That’s why you can change themes without loosing content. You database backup is done differently than the theme.

I do understand the difference as i work in joomla alot and it has the same aspects.

All i am trying to do is update the site to 3.0 and keep all postings. It seems to me that the issue is with comments, We are fine with losing those.

If you go to the site you can see the theme we have is the defult one anyways so upgrading to 3.0 and haveing a new theme is also ok.

My question is this.

Can i either fix this error and upgrade to 3.0

OR

Will upgrading to 3.0 overwrite the bad entry(s) in the database.

Thank you

Kyle

No my client did.

I am a reseller for hostgator (We resell webhosting and do webdesign)

As for the backup would that undo any changes and postings for the last 6+ months? If so, that wont be possable.

Now that i am managing their site backups will be a primary focus.

Is there a chance this will fix its self if we upgrade? MY goal is to get them updated to the most current version of word press

Thanks

Thanks for the quick reply

I went back in and repaired all the tables. Still showing that error.

Any other ideas?