• Hi,

    To cut a long story short, I am now getting a ‘Site Not Found – The site you have requested does not exist on this server’ error message when trying to visit my blog (https://thestarchamber.mattkeefe.com). Here’s the full story…

    Having had some problems trying to upgrade to 2.7, it became necessary for me to do a full install – I deleted the old installation, installed 2.7 from scratch then restored my old database. However, there was one problem in that the tables in my back-up database had the table prefix ‘thestarchamber’ – e.g. ‘thestarchamberusers’ or ‘thestarchamberposts’ and so on – rather than the usual ‘wp_’ prefix. I couldn’t figure out how to get the wordpress software to recognise the restored tables, so I simply renamed them with the ‘wp_’ prefix. This seemed to work – wordpress found all my old posts, comments and other data, and I had the blog up and running as before – until now, approximately 12-16 hours later, when I’ve received the error message described above.

    There were other slight glitches in the meantime – for instance, a post I had scheduled for 1200 (GMT) today did not post for some reason. I’m wondering now if renaming the tables created problems I wasn’t aware of – it was a quick fix to get the old content restored, but it did break down some hidden links between the data that I’m unaware of?

    I wonder now if, rather than renaming the tables, to the ‘wp_’ prefix, I should have redirected the new wordpress installation towards those tables with the ‘thestarchamber’ prefix. But how would I do this? By altering the $table_prefix = ‘wp_’; line in the wp-config.php? Incidentally, I now notice that even though I had installed wordpress and had the blog up and running, the wp-config.php on my server is in exactly the same state as when I first entered the database information. Am I right in thinking that this should not be the case, and that in installing wordpress the wp-config.php file should have been substantially altered? Is it possibly the case that through restoring the db tables in the way I did, I actually prevented wordpress from completely ‘installing’, so to speak?

    Either way, what’s the solution?

    Many thanks,

    Matt

Viewing 2 replies - 1 through 2 (of 2 total)
  • However, there was one problem in that the tables in my back-up database had the table prefix ‘thestarchamber’ – e.g.

    That’s not a problem…you just enter that prefix in your wp-config.php file and it will find the tables. If you think that you may have damaged something by editing your database, then I would suggest dropping those tables and importing your original database without changing those prefixes.

    There were other slight glitches in the meantime – for instance, a post I had scheduled for 1200 (GMT) today did not post for some reason.

    There have been quite a few people reporting problems with scheduled posts not posting…search the forums here…this may have nothing to do with your install.

    I deleted the old installation, installed 2.7 from scratch

    Are you sure that you reinstalled WP in the exact same location as your previous blog? If not, then you may need to change the address (path) in your database file.

    Thread Starter matt-keefe

    (@matt-keefe)

    Hi Figaro – thanks for the swift reply!

    Yeah, I certainly reinstalled WP in the exact same location. I’ll discount the problem with the scheduling as something unrelated and I’ll try restoring the db tables again then editing the config.php.

    Thanks,

    Matt

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Problems after restoring database’ is closed to new replies.