Hi,
can you explain your structure a bit more? Just from reading it it sounds like you tried to install WP in a sub folder of an already existing WP installation. and that you were trying to use the same DB for both WP installations.
so, if you could explain the structure a bit more that would help.
I can try!
So I have an existing WordPress site hosted by hostway.com. I want to keep that site up while I build a new one. I was told I could do so by using a subdirectory (mysite.com/subdirectory). So I clicked on the WP icon on my hosting site and in filling out all of the information created a subdirectory. They are both on the same mySQL database.
so mysite.com is a blank page
mysite.com/subdirectory is now like a cached version of the welcome page from WP
mysite.com/wp-admin reroutes to an update wordpress database
mysite.com/subdirectory/wp-admin was working until I changed something else and is now a blank page
I think I’ve tried so many different things that I’ve completely screwed it up. It’s time to call in help.
mysite.com/subdirectory/wp-admin was working until I changed something else
What exactly did you change?
alright, starting to see what you were trying to do.
quick question, did you setup a new database on the same mysql server to house the new WP installation? or did you use the same existing WP database for the new installation?
If you did, you probably overwrote some data that was making your original site function.
I don’t see much of a problem in the concept of what you’re trying to do, but let me say that it would make more since to have both of the sites in their own sub-directories. This way they would be seperate, but equal. Also, this would’ve only needed a couple of changes made on your hosting configuration.
What I’d recommend at this point is to restore from backup. Remove the new installation completely and put everything back like it was. If you haven’t done this before, just let me know and I can help as much as I can.
From there, create a new sub-folder and a new database (separate from the existing one) and attempt installing the new WP installation into the new sub-folder.
Jeb,
You are correct that I used the same existing database and that is the entire mess up that I made.
I spoke with a WP Developer who fixed as much as she could but said that I need to have the hosting company restore the database to a few days ago.
I just got off the phone with them and they want $99/month for that service. I think that is outrageous and cannot afford that. I asked them if I could remove the new installation from the database and she said that wasn’t an option.
A separate database costs an additional $15/month. This is the worst hosting company ever!
that really sucks!
do you have a backup of your data anywhere?
here is a link to the codex that explains backup options. if your host allows you to create cron jobs, there are linux scheduled tasks, then you could script out a backup routine and have it sftp’d off to a secure location.
Backing Up your Database
I have a backup of the public_html and web folders in FTP but that’s it. Can I do anything with that?
I would love to switch hosting companies at this point, if I can just get my site back first.
99% of your site’s content was/is stored in your database – not in any folders. Without a database backup from before you made these “changes”, your content is toast. Your only other option is to pay the hosting company restore the database.
hmmm…….
having all of the files is certainly going to help. that way you won’t loose any custom themes/coding that you’ve done.
second, and correct me if I’m wrong esmi, but i think it should be possible to pull out, provided it wasn’t droped, all of the posts and other data from the existing database.
now – if you look and you see that the database is empty – that is a much bigger problem. BUT! if your original site’s data is still in the database, then it should be possible to pull that out and save it – before attempting to do anything else.
take a look and let us know if you see any of your original data in the database.
The OP used the same db. If he didn’t use different table prefixes, then it’s likely that his hosts’ 1-click installer emptied the db before re-installing. The only way to know for sure would be to physically examine the database in question – which, I would assume, his WP dev has already done.
esmi –
just so I understand you correctly, when a WP is installed and attempts/creates the DB – it will do a drop and recreate of the tables?
what if the person decides to use a different prefix for the tables? will the script preform a drop all tables?
If not, and provided that reganinc used different prefixes then the data might still be there.
Thank you both for helping me out with this. I ended up calling them back and asked them to do the restore. I would really like to change hosting sites after this is all fixed.. do either of you have any good recommendations?
when a WP is installed and attempts/creates the DB – it will do a drop and recreate of the tables?
No. A manual re-install will stop immediately and tell you that WP is already installed. You have to go create your own wp-config.php with all of the db details – including a different db table prefix – before WP will be persuaded to continue with an install.
WP itself will never drop or over-write tables.
However… some of the generic 1-click installers that I’ve seen allow you to carry out a “re-install” via their ui – which seems to consist (sometimes) of dropping tables and then letting the native app take over as if it’s a brand new install. In that situation, WP would proceed as if this was a brand new install.
Obviously, I can’t say for sure without checking the db myself but it’s a possibility.
Although we do not personally endorse them, there are some hosts listed here. Also searching the forums using the keywords “host” or “hosting” may provide you with some suggestions.
And, in future, I would strongly recommend that you start making your own database backups instead of relying on your hosts. It’s not as scary as it sounds. Not all hosts charge to restore a database but I can fully understand why some do. If you wreck your database, or fail to back it up, it’s not really their fault. Always protect and back up your own data.
