In hopes of sluthing out a major error, I installed ZC twice. the second time i used the first databse but none pf my products are showing up or settings?
How can I merge DB #1 into Zen Cart #2??
In hopes of sluthing out a major error, I installed ZC twice. the second time i used the first databse but none pf my products are showing up or settings?
How can I merge DB #1 into Zen Cart #2??
Did you "install" the second time, or "upgrade"? The database phase of zc_install has a prominent warning above the "install" and "upgrade" buttons that installing will wipe any content in the database. You need to choose "upgrade". If you didn't have a current backup of your db, you have probably lost all of its content permanently.
So did you just put the files in place for the second one, without running zc_install? If the second store was actually connected to the first database, it ought to function the same. What things did you configure for the second store?
If you want to test some anomaly in your original setup, it would be better and safer to install a new store on a new db, then export the db from the old and import it into the new. That way you start with an exact duplicate which you can play with without fear of hurting your real store.
Thanks...although DB 1 is doing just fine on ZC 1 and 3, I still think this version of zen just is messed up for downloads.
This is my error: http://templatetonic.com/ipage.jpg
![]()
ZC1.5.0 has gone through a long public debugging phase before being officially released, so I doubt there is a problem with the original code. Something (no idea what) must have gotten corrupted in your installation #2.
And the fact remains that any testing you do on #3 in admin will also affect #1. A separate copy of the db is far safer.
Maybe so. Maybe not.
It happened to someone else too. See here: http://www.zen-cart.com/forum/showth...00#post1098400
Sounds like some kind of interference between Chrome's handling and Zen Cart's code... if it is a real, reproducible effect, someone will get to the bottom of it and find out why it is happening, and which party ought to change (if Chrome is mishandling valid code, it will affect anybody who uses it, not just ZC).