March 3, 2012 at 3:21 pm #5741
I’m not sure how else to summarize that! lol
I moved my site to a new host. I have multiple other WP installations, and have them up and running. But the installation that eStore is in is behaving oddly. I moved over the files, updated wp-config, imported the old database tables, and updated the wp-options that point to the domain name. The main page of the site comes up fine at first, but as soon as I click on a link, I get a “database connection error,” and the whole database is screwed up.
If I go into PhpMyAdmin after that, to look at the database, what I see is no longer the same. All of the regular tables are missing, and I can’t even select the database name. Because it’s only the WP eStore installation that’s doing this, I wonder if it’s somehow connected to some settings in the eStore portion of the database. (I tried deleting the database, recreating it, and re-importing the tables. The same thing happened.)
If I have to install again from scratch, I can do that, but I’d rather not lose all of my information. Is there some other way to import my settings, user info, product information, etc., besides importing the whole database?March 3, 2012 at 11:32 pm #42654
Too many things can go wrong when moving servers if the database tables are not transferred correctly. This post will shed some light:
Here is another related post on this topic:
Also, if you are having trouble then don’t transfer the eStore tables from your old server. Do the following:
1. Activate a new copy of eStore on your new server (this will create new tables)
2. Export the product and other table data from the old server
3. Import them to this new server
4. Follow this video tutorial which will help:
Also, go through your settings items in eStore and update the URL values accordingly too.March 4, 2012 at 8:25 pm #42655
I don’t understand this response. It sounds like you are telling me to do what I already did. And I don’t understand how “option 2” is different from the first way of doing it. What I have done so far is:
1. Exported ALL of the tables from the database that holds the original WP installation, using PHPMyAdmin. (Not just the original WP tables, and not through the WP dashboard.)
2. Moved (copied) all of the files from the old cpanel file manager to the new one.
3. Created a new database and user on the new server.
4. Updated wp-config to have the new database values.
5. Used PHPMyAdmin to go in and change the root URL’s in the WP options. (So URL’s should now reflect the new server.)
6. Visited the new site. Here’s where it gets wonky. Up to this point, all of the database tables are present on the new server. But then…
7. Clicked on a post link. NOW I get a database connection error, and if I go back to PHPMyAdmin, all of the tables are gone. THEY WERE THERE until I clicked on a link in the site.
So you can please clarify what OTHER way I should be migrating the database tables to the new server? And what you mean by “not transferring them,” if I’m having trouble, but exporting and importing them?
Thank you!March 5, 2012 at 1:17 am #42656
Sorry if my answer was unclear. We can’t really know what has gone wrong with your server migration so we won’t be able to just give a solution (this is beyond the scope of our standard plugin support). All we can tell you is that there is no special requirement needed for our plugin when you migrate your hosting. Lot of users are doing it.
If you want us to investigate your site and provide help, then you can use the following option:
What I meant in the previous post is that you can try transferring only the *content* of the eStore tables. So you install a fresh copy of the plugin in the new server which will create all the tables (it will just be empty as it doesn’t have any product information). You then export the content (product information) from the old server in a CSV file for example and then import that product information in the new server’s empty table.
Again, this is beyond the scope but I will give a quick explanation as to why I recommended that method. When you go to a new host it will have a different database name prefix for your WordPress database than your old host (you can’t see this but know that the full qualified database table name will be different). Hosting companies automatically generate a unique database prefix in order to make sure there is no name conflicts between multiple accounts that are hosted on this same server. If your tables have reference to the old database tables full qualified name it will have a hard time making a connection because on the new server this name has changed. One easy way to get around this issue is to transfer only the *content* of the tables (not the table with the content).March 5, 2012 at 9:48 pm #42657
I think I understand now. Thank you for clarifying!
Will it be obvious, when I view the tables in PHPMyAdmin, which ones are connected to eStore?March 6, 2012 at 12:41 am #42658
The ones that have the “eStore” keyword in their name.March 13, 2012 at 4:04 pm #42659
This worked beautifully. Thank you!
- You must be logged in to reply to this topic.