September 26, 2012 at 9:45 pm #7495
I know this is no news to you, so I’ll skim trough it:
— developed locally, on my Windows box, on top of XAMPP;
— using mysqldump I moved the WordPress database to the production server, a Fedora;
— double checked and seemingly the eStore tables have been copied, namely:
— yet, I have no products nor categories in the admin panel, BUT I am able to create
So, my questions are two:
1. Why is it happening?
2. How can I bring back my products and categories WITHOUT reentering them.
Claudius Tiberiu IacobSeptember 26, 2012 at 9:54 pm #49763
Looked into the “wp_wp_estore_tbl” and found that my old products (the ones that I defined on my Windows box) are still there.
However, I defined a test product here, on Linux, and this one does not show in this “wp_wp_estore_tbl” table, although it does show in the admin panel.
I must specify that I used the same MySQL user to consult the tables as WordPress does.
PLease shed some light on that.September 26, 2012 at 10:05 pm #49764wzpModeratorSeptember 27, 2012 at 8:28 am #49765
Thanks wzp, been there before starting the thread.
Maybe I can shed some light on that myself:
1) The tables that got transfered via mysqldump/restore (well, in fact created from scratch, because that’s how the thing works are the following) (copy/paste from the mysql monitor prompt):
| wp_wp_estore_tbl |
… and a few others
For some reason, the plugin couldn’t read from any of these, so after deactivating and re-activating it, has created a brand new set of tables, with these names:
| wp_wp_eStore_tbl |
… and a few others
That is, an uppercase “S” in “eStore”, as oposed to a lower case “s” in “estore”.
Now, my question is: why did the plugin expected to find a table named “…eStore…” instead of “…estore…” as soon as the website moved to Linux? Key Master, do you have a word on this?
ThanksSeptember 27, 2012 at 9:45 am #49766
Ok, so just to keep you posted: I dropped all the tables starting with “eStore” and renamed the old ones from “estore” into “eStore”, and now I have access to my old data.
Still, I’m really keen to find out why this thing happens. And a fix in a next version would be nice also
ClaudiusSeptember 27, 2012 at 12:31 pm #49767wzpModerator
Linux is correct; it is supposed to be “eStore” NOT “estore”. I suspect that moving from a non case sensitive (Windows) to a case sensitive (Linux) environment caused that issue.
Have you considered just exporting and then importing your products via a CSV file? Doing so might avoid table naming issues.
- You must be logged in to reply to this topic.