coreym

I am working out the deployment procedures required to migrate changes from a development environment to a production environment. The simplified flow below intentionally ignores test and staging for brevity. The flow is similar to the following: Step 1: Clone production site to development server This creates a point in time snapshop of the production environment to begin new modifications. Step 2: Modify theme, store configurations, install modules, etc. Everything but product, customer, and order related tables are modified. Only core and module tables, along with theme code is changed here. Step 3: Migrate core system, theme and module modifications to production. Push all core & module changes to production overwritting production core and module tables, and push all new code / theme code to production. No customer, order, or product data is modified. Step 4: Start over from Step 1 when new core system, theme, or module modifications are required. For step three I would like to only migrate the non-customer / order / product related tables. My question: Does anyone have a list of which tables are required for customer, order, and product functionality so that I can exclude those from the migration scripts?

I am working out the deployment procedures required to migrate changes from a development environment to a production environment. The simplified flow below intentionally ignores test and staging for brevity. The flow is similar to the following: Step 1: Clone production site to development server This creates a point in time snapshop of the production environment to begin new modifications. Step 2: Modify theme, store configurations, install modules, etc. Everything but product, customer, and order related tables are modified. Only core and module tables, along with theme code is changed here. Step 3: Migrate core system, theme and module modifications to production. Push all core & module changes to production overwritting production core and module tables, and push all new code / theme code to production. No customer, order, or product data is modified. Step 4: Start over from Step 1 when new core system, theme, or module modifications are required. For step three I would like to only migrate the non-customer / order / product related tables. My question: Does anyone have a list of which tables are required for customer, order, and product functionality so that I can exclude those from the migration scripts?

ok, thanks. Any reason why every row is set to NULL on a fresh install?

I would like to add to this. We are using homeslider v1.4.3. We have the same issue as undiscovered33 and the same solution works. But I want to figure out why saving the homeslider config always creates these incorrect entries in ps_configuration: +------------------+---------------+---------+-------------------+-------+---------------------+---------------------+ | id_configuration | id_shop_group | id_shop | name | value | date_add | date_upd | +------------------+---------------+---------+-------------------+-------+---------------------+---------------------+ | 228 | NULL | NULL | HOMESLIDER_WIDTH | 779 | 2015-01-16 16:45:30 | 2015-01-16 17:22:56 | | 229 | NULL | NULL | HOMESLIDER_HEIGHT | 300 | 0000-00-00 00:00:00 | 0000-00-00 00:00:00 | | 230 | NULL | NULL | HOMESLIDER_SPEED | 500 | 0000-00-00 00:00:00 | 2015-01-08 12:52:43 | | 231 | NULL | NULL | HOMESLIDER_PAUSE | 3000 | 0000-00-00 00:00:00 | 2015-01-08 12:52:43 | | 232 | NULL | NULL | HOMESLIDER_LOOP | 1 | 0000-00-00 00:00:00 | 0000-00-00 00:00:00 | | 417 | 1 | 1 | HOMESLIDER_LOOP | 1 | 2015-01-16 17:16:42 | 2015-01-16 17:22:56 | | 418 | 1 | 1 | HOMESLIDER_WIDTH | 1300 | 2015-01-16 17:27:18 | 2015-01-16 17:27:18 | +------------------+---------------+---------+-------------------+-------+---------------------+---------------------+ The entries with id_shop, and id_shop_group set to NULL are the ones being used by homeslider. But the two rows with id_shop, and id_shop_group set to 1 are created when saving from the homeslider config screen. Manually setting the id_shop=NULL HOMESLIDER_WIDTH to 1300 changes the way the module behaves, but I cannot change the value using the homeslider config screen. All other rows in ps_configuration have id_shop and id_shop_group set to NULL. Why is homeslider creating these two new rows with the id_shop, and id_shop_group set to 1? Thanks, Corey

Is there a way to upgrade using a script like we can with the install process? http://doc.prestashop.com/display/PS16/Installing+PrestaShop+using+the+command-line+script This would be useful for automating the upgrade of multiple PS installs (which is my situation).