spminis:
Thanks for your input.
You're probably correct and I did think about that because after I did a clean install of ZC, I then uploaded the db from my live store. I thought about experimenting by installing the template without uploading the db. The problem is that if it works, I would still have a problem installing the template in my live store and frankly, I don't want to mess with that db and I don't want to bother going through the trouble of doing so.
Carol
Westminster_new is a lot more detailed and "complex" than picaflor's earlier templates. There is a lot more activity going on behind the scenes, and it looks like there are a lot of conflicts going on with the way your original site is communicating with the database, and then having to cope with more detailed westminster_new template. Much of this is caused by old plugins that are either edits of some core files, or have redundant overrides.
We had a look at the basic structure and much of the code in the westminster_new template and decided to REMOVE practically every plugin we were using on the original site (both front-end and admin plugins), before implementing this new template.
After a couple of days, and much discussion, we decided to (on a dev server), a completely fresh install of ZC:1.5.5b (a few days later to become ver.c then ver.d) - with a fresh and empty database - as if we were "starting for the first time"..
Then, we looked for ESSENTIAL plugins compatible witn 1.5.x (for admin & front-end) and installed these. So we still had a totally empty site (no products, no customer data, no transaction data.)
Then, we matched up (as far as we could) the ADMIN configurations that existed in the old "live" site, with the new "dev" site... This included all the parameters in the "configuraton" menu, along with payment and shipping modules. We loaded up sitemap.xml, Ceon URI re-write, Google Merchant Center, EasyPopulate V4, Export Shipping Orders, CK Editor.
When we had the new dev site configured as closely as possible to the working, original site, we did database dumps of both sites' databases and did a very careful analysis of the tables. Many plugins make changes to the dbase, and we found that even after using uninstall.sql files, many tables were in a "mess". (Fortunately, we have fairly good MySql skills available).
Then... we TRUNCATED all the tables in the dbase relating to products, customers, addresses, orders, ... In other words, all tables where PRODUCT, CUSTOMER and TRANSACTIONAL data is stored (and cross-referenced). To do this, one needs to know the relational nature of the various tables, so it's not something a novice should attempt.
Then we INSERTED the data from the live (now under maintenance) stores database, into the NEW store database - thereby transferring all customer and product-related data from the old site, to the new site.
I must stress this is NOT for novices... One tiny error in a Dbase ID number, and you are in a total mess.
Then... better part of a day doing testing. Apart from a few minor glitches (oversights really), the new site "replaced" the old site just 72 hours later, with a total "down for maintenance" time of just over an hour.