Is there an easy way to copy your customer database from one cart to another cart KEEPING BOTH active carts?
Is there an easy way to copy your customer database from one cart to another cart KEEPING BOTH active carts?
Well, here is an update on things.
I have been pulling parts of the database using phpmyadmin. Certain parts are of it (such as zc_admin) will break the cart install as it will display "WARNING: An Error occurred, please refresh the page and try again."
Is there something that I should be doing with these database files so that they will go from 1.5.0 to 1.5.1 without crashing the cart?
well, I finally figured out what needed to be done to get this working.
I needed to go and pull the database files, open up notepad++, find and replace all things that were not current which were:
-server location which was named "home" in my original install, but my new install called the folder "home1"
-change the name of the catalog which I named something different in the original 139 to the same thing in the new install that it was going to be planted in so everything matched the new locations.
-looked for DROP TABLE if...looked for prefix, and changed it to the new install prefix
-same as above for Create Table if not exist
-did a find for "zen_" and had to change it to match my new install of 151 which listed it as "zc_"
After that, I saved the file, went into phpMyAdmin, selected all, dropped, then clicked on Import and imported this db that I edited inside of notepad++
No error occurred after importing as if there was an issue, phpmyadmin would tell you.
Then I checked my cart, it showed up. When I went to go into the admin panel, it didn't give me a login screen, but only said that I needed to update my database from 139 to 151.
I then navigated inside my browser and found zc_install and ran the database update. Once this was finished, SUCCESS, I got my login screen for the admin panel.
I hope this helps anyone who also had the same issues that I was having. Thanks to other posts where I was able to get a direction on where to look to fix this. Thanks to the Zelda Avatar person, "Ajeh". You posted some info (I cant find the thread right now) where you said something that made me go in my direction to solve this.
and this link was also helpful: http://stackoverflow.com/questions/8...hin-phpmyadmin
I have been doing it a bit differently using phpMyAdmin to pull only products, customers and information that will not affect your updated version installation.
Instead of importing the entire database, select the database table you want to export from the old database by clicking on the titles along the left side. Then when you look at the center it should say just that database file i.e. zen_categories_description then go to top and click export, you want to export to sql at the bottom click save as and I make a new folder called ProductFiles and I saved all the sql for the selected areas of the database pertaining to products, customers, categories, and their perspective descriptions files.
Then when you are done downloading all the files you go to the new database select from the list on the left side again here. This time when you select a table if there is information in the center (sample info) scroll down and click check all and delete all the sample information before going to the top and importing the sql files that you saved for the listing. This will insure that it doesn't show as a duplicate.
Time consuming? Yes, but worth it especially when if like me you are developing a bald spot in your head just from having to undertake the upgrade process to begin with. But at least this way you should not disrupt the new version core database functions and still keep your products and customer files intact.
Readers should be aware that these procedures are very risky, and if not done completely and exactly right will corrupt your database.
The recommended method which works in practically every case when followed correctly is to import the entire database and let zc_install upgrade it to the new version. I don't know if there are any changes to the tables described for v1.5.x, but if there are they need to go through the upgrade process to be made right.
I would, using the principle above, create a third database into which to load the table(s) being migrated. Then use a copy of zc that works (also a third location) to do the uupgrade on. Then transfer the ddata from the new/temporary location into the 151 database.
This way at no time would the active store have "old" data that could disrupt the activities of an online guest.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
Bookmarks