Jump to content

Rynraf

Members
  • Content count

    18
  • Joined

  • Last visited

About Rynraf

  • Rank
    PrestaShop Newbie

Profile Information

  • Gender
    Male
  • Location
    Poland

Contact Methods

  • Website URL
    https://palmatum.pl
  • Facebook
    https://www.facebook.com/palmatum.bonsai/

Recent Profile Visitors

70 profile views
  1. jmeca, I've tested PS version 1.7. This version have few changes, few functionalities which are important for me and doesn't exist in PS 1.6 I've also tested all using by me modules on new Prestashop. Of course - it's my opinion and my choice In my opinion now PS 1.7 is better. It's not only about stable but about new functionalities (order and product managment). I will give PS 1.7 a chance Regards!
  2. Why manually? Because I don't trust automated migration where data are complex and important. Also I would like to have control and awareness of whole process. Also thanks to this process I can find and remove some not necessary or redundant data. Regards!
  3. Non-developer experience This tutorial was created by me step by step. I'm not a Prestashop developer. I just use it. I decided finally to migrat data between versions by my own and test everything before release on production environment. I wrote this, tested and I can promise - it works It tooks me many hours Doubtless because earlier I didn't know Pestashop database structure, relationships. Below what I have tested. I'm know that in below description step by step I'm not included all data migration. For example I don't use attachments to products in my shop.But most of it and all which was important for me. I tested this on migration from 1.6.0.14 to 1.7.2.2 First iteration - check whole process. Second - do this finally and at the beggining switch your shop to maintanance mode. I suggest to do this this way: a) Install Prestashop 1.7 in different place (could be on dedicated subdomain). It's better to install it on different database but it's not necessary becuase we will use different prefixes in table names. For PS 1.7 installation I set tables prefix "ps17". If you need - install additional language. In my case described here I added one additional language. You can do this in backoffice here: International > Localization > Import a localization pack Copy migrated tables (list below) from production (PS 1.6) database to Prestashop 1.7 database. I assume that in PS 1.6 we have tables with default prefix "ps". If you decided to work on the same database with two versions of PS - you can just make copies of this tables. c) Export below 82 tables from PS 1.6 database. You can do this manually using for example phpMyAdmin (web application) or HeidiSQL (standalone desktop application) - chosing one by one tables and export them. OR you can automate this using this library: https://github.com/ifsnop/mysqldump-php (example here: https://stackoverflow.com/questions/18167769/backup-databases-using-query-without-using-mysqldump). More irritating but easier is dump export tables from phpMyAdmin d) Rename oryginal 82 tables in Prestashop 1.7 to leave copies of them. I just added "_oryg" suffix to them. You have SQL query prepared by me. e) Import exported earlier tables from PS 1.6 to PS 1.7 database. Just import. f) Imported tables - change their prefix from "ps_" to "ps17_". Use prepared sql query. g) Make changes in tables on Prestashop 1.7 database. h) Update language ID - optional. If you have more than one language in your shop and after installation new one in PS 1.7 is different ID of it in database. i) Copy whole folder /img/p/ from PS 1.6 to PS 1.7 location. Also /img/c/ (categories) and /img/s/ (carriers). j) Test migration on duplicated shop. Set all settings, images, theme (remamber after this process you have oryginal PS 1.7 theme) etc. Of course data migration is not enough to start new shop k) Move your copy of Prestashop to production to replace it (the best solution will be changing the place where your domain indicate on your server, make shop copy on production to have two copies of them and change only one - regarding this in any case you can still switch to last Prestashop version only by changing domain settings) or go through the same steps on your production shop as you done before on copy. l) In my case I have to set filter (on categories) settings. Go to back office (Modules > Installed Modules > Faceted search) and set them. Activate and choose style of field. Next step - rebuild in the same module price and attribute index. Don't forget to set categories for which this filter is active m) I'm also not move another module setting - main menu module. In backoffice go to Modules > Installed Modules and find "Main menu" module and choose which categories would you like to present. n) Rebuild your search engine index after all. In backoffice go to Shop Parameters > Search and click on link "Re-build the entire index". ......................................... c) List of transformed and moved tables in whole process. Export them to sql text file dump. ##categories copy folder /img/c/ ps_category ps_category_group - I use default groups and I don't need to migrate this table. ps_category_lang ps_category_product ps_category_shop ##customer groups I'm using default groups... but if you use this functionality - this are tables related to this topic. There are no changes in this tables structure. ps_group ps_group_lang ps_group_reduction ps_group_shop ##customers and orders ps_customer ps_customer_group ps_orders ps_order_detail ps_order_invoice ps_order_carrier (just copy, no changes in table structure) ps_order_cart_rule (just copy, no changes in table structure) ps_order_detail_tax (just copy, no changes in table structure) ps_order_history (just copy, no changes in table structure) ps_order_invoice_payment (just copy, no changes in table structure) ps_order_invoice_tax (just copy, no changes in table structure) ps_order_message (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. Maybe you too. ps_order_message_lang (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. ps_order_payment (just copy, no changes in table structure) ps_order_return (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. ps_order_return_detail (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. ps_order_return_state (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. ps_order_return_state_lang (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. ps_order_slip (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. ps_order_slip_detail (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. ps_order_slip_detail_tax (just copy, no changes in table structure) I'm not using this table then I don't need to migrate it. ps_order_state (just copy, no changes in table structure) ps_order_state_lang (just copy, no changes in table structure) ##currencies ps_currency (some structure changes - we should remove few columns) ps_currency_shop (just copy, no changes in table structure) ps_image ps_image_lang ps_image_shop ##products ps_product ps_product_attribute (some structure changes, below) ps_product_attribute_shop (some structure changes, below) ps_product_download ps_product_lang ps_product_shop ps_product_tag ps_tag ps_specific_price (some structure changes, below) ps_specific_price_priority (just copy, no changes in table structure) ps_specific_price_rule (just copy, no changes in table structure) ps_specific_price_rule_condition (just copy, no changes in table structure) ps_specific_price_rule_condition_group (just copy, no changes in table structure) ps_stock_available ##product combinations: ps_product_attribute_combination (just copy, no changes in table structure) ps_product_attribute_image (just copy, no changes in table structure) ps_attribute (tylko przekopiować) ps_attribute_group (just copy, no changes in table structure) ps_attribute_group_lang (just copy, no changes in table structure) ps_attribute_group_shop (just copy, no changes in table structure) ps_attribute_impact (I have no data in this table) ps_attribute_lang (just copy, no changes in table structure) ps_attribute_shop (just copy, no changes in table structure) ps_layered_product_attribute ##related products: ps_accessory (just copy, no changes in table structure) ##product features: ps_feature (just copy, no changes in table structure) ps_feature_lang (just copy, no changes in table structure) ps_feature_product (just copy, no changes in table structure) ps_feature_shop (just copy, no changes in table structure) ps_feature_value (just copy, no changes in table structure) ps_feature_value_lang (just copy, no changes in table structure) ##carriers and what implicate copy folder /img/s/ Important! Check if tax ids (in my case - tax ID are the same) and zones IDs are the same. If not - sorry, you need to update it or give up of migrating carriers settings and set if from the beggining in new shop - it's possible alternative. ps_product_carrier (just copy, no changes in table structure) ps_carrier (just copy, no changes in table structure) ps_carrier_group (just copy, no changes in table structure) ps_carrier_lang (just copy, no changes in table structure) ps_carrier_shop (just copy, no changes in table structure) ps_carrier_tax_rules_group_shop (just copy, no changes in table structure) ps_carrier_zone (just copy, no changes in table structure) ps_delivery (just copy, no changes in table structure) /what implicates on below tables: ps_range_price (just copy, no changes in table structure) ps_range_weight (just copy, no changes in table structure) ps_zone (just copy, no changes in table structure) ps_zone_shop (just copy, no changes in table structure) ps_tax (just copy, no changes in table structure) /identyczne dane ps_tax_lang (just copy, no changes in table structure) ps_tax_rule (just copy, no changes in table structure) ps_tax_rules_group (just copy, no changes in table structure) ps_tax_rules_group_shop (just copy, no changes in table structure) /I don't need to move or change this table. The same content I have in old PS 1.6 and in PS 1.7 d) In any case - I will leave in the same database copy of changed / migrated tables. We will just add suffix "_oryg" to this tables. RENAME TABLE ps17_category TO ps17_category_oryg; RENAME TABLE ps17_category_lang TO ps17_category_lang_oryg; RENAME TABLE ps17_category_product TO ps17_category_product_oryg; RENAME TABLE ps17_category_shop TO ps17_category_shop_oryg; RENAME TABLE ps17_customer TO ps17_customer_oryg; RENAME TABLE ps17_customer_group TO ps17_customer_group_oryg; RENAME TABLE ps17_image_shop TO ps17_image_shop_oryg; RENAME TABLE ps17_orders TO ps17_orders_oryg; RENAME TABLE ps17_order_detail TO ps17_order_detail_oryg; RENAME TABLE ps17_order_invoice TO ps17_order_invoice_oryg; RENAME TABLE ps17_product TO ps17_product_oryg; RENAME TABLE ps17_product_attribute TO ps17_product_attribute_oryg; RENAME TABLE ps17_product_attribute_shop TO ps17_product_attribute_shop_oryg; RENAME TABLE ps17_product_download TO ps17_product_download_oryg; RENAME TABLE ps17_product_shop TO ps17_product_shop_oryg; RENAME TABLE ps17_product_tag TO ps17_product_tag_oryg; RENAME TABLE ps17_specific_price TO ps17_specific_price_oryg; RENAME TABLE ps17_specific_price_priority TO ps17_specific_price_priority_oryg; RENAME TABLE ps17_specific_price_rule TO ps17_specific_price_rule_oryg; RENAME TABLE ps17_specific_price_rule_condition TO ps17_specific_price_rule_condition_oryg; RENAME TABLE ps17_specific_price_rule_condition_group TO ps17_specific_price_rule_condition_group_oryg; RENAME TABLE ps17_product_lang TO ps17_product_lang_oryg; RENAME TABLE ps17_image TO ps17_image_oryg; RENAME TABLE ps17_image_lang TO ps17_image_lang_oryg; RENAME TABLE ps17_category_group TO ps17_category_group_oryg; RENAME TABLE ps17_stock_available TO ps17_stock_available_oryg; RENAME TABLE ps17_tag TO ps17_tag_oryg; RENAME TABLE ps17_product_attribute_image TO ps17_product_attribute_image_oryg; RENAME TABLE ps17_product_attribute_combination TO ps17_product_attribute_combination_oryg; RENAME TABLE ps17_attribute TO ps17_attribute_oryg; RENAME TABLE ps17_attribute_group TO ps17_attribute_group_oryg; RENAME TABLE ps17_attribute_group_lang TO ps17_attribute_group_lang_oryg; RENAME TABLE ps17_attribute_group_shop TO ps17_attribute_group_shop_oryg; RENAME TABLE ps17_attribute_lang TO ps17_attribute_lang_oryg; RENAME TABLE ps17_attribute_shop TO ps17_attribute_shop_oryg; RENAME TABLE ps17_accessory TO ps17_accessory_oryg; RENAME TABLE ps17_feature TO ps17_feature_oryg; RENAME TABLE ps17_feature_lang TO ps17_feature_lang_oryg; RENAME TABLE ps17_feature_product TO ps17_feature_product_oryg; RENAME TABLE ps17_feature_shop TO ps17_feature_shop_oryg; RENAME TABLE ps17_feature_value TO ps17_feature_value_oryg; RENAME TABLE ps17_feature_value_lang TO ps17_feature_value_lang_oryg; RENAME TABLE ps17_layered_product_attribute TO ps17_layered_product_attribute_oryg; RENAME TABLE ps17_product_carrier TO ps17_product_carrier_oryg; RENAME TABLE ps17_carrier TO ps17_carrier_oryg; RENAME TABLE ps17_carrier_group TO ps17_carrier_group_oryg; RENAME TABLE ps17_carrier_lang TO ps17_carrier_lang_oryg; RENAME TABLE ps17_carrier_shop TO ps17_carrier_shop_oryg; RENAME TABLE ps17_carrier_tax_rules_group_shop TO ps17_carrier_tax_rules_group_shop_oryg; RENAME TABLE ps17_carrier_zone TO ps17_carrier_zone_oryg; RENAME TABLE ps17_delivery TO ps17_delivery_oryg; RENAME TABLE ps17_range_price TO ps17_range_price_oryg; RENAME TABLE ps17_range_weight TO ps17_range_weight_oryg; /* step */ RENAME TABLE ps17_zone TO ps17_zone_oryg; RENAME TABLE ps17_zone_shop TO ps17_zone_shop_oryg; RENAME TABLE ps17_tax TO ps17_tax_oryg; RENAME TABLE ps17_tax_lang TO ps17_tax_lang_oryg; RENAME TABLE ps17_tax_rule TO ps17_tax_rule_oryg; RENAME TABLE ps17_tax_rules_group TO ps17_tax_rules_group_oryg; RENAME TABLE ps17_tax_rules_group_shop TO ps17_tax_rules_group_shop_oryg; RENAME TABLE ps17_currency TO ps17_currency_oryg; RENAME TABLE ps17_currency_shop TO ps17_currency_shop_oryg; RENAME TABLE ps17_group TO ps17_group_oryg; RENAME TABLE ps17_group_lang TO ps17_group_lang_oryg; RENAME TABLE ps17_group_reduction TO ps17_group_reduction_oryg; RENAME TABLE ps17_group_shop TO ps17_group_shop_oryg; RENAME TABLE ps17_order_carrier TO ps17_order_carrier_oryg; RENAME TABLE ps17_order_cart_rule TO ps17_order_cart_rule_oryg; RENAME TABLE ps17_order_detail_tax TO ps17_order_detail_tax_oryg; RENAME TABLE ps17_order_history TO ps17_order_history_oryg; RENAME TABLE ps17_order_invoice_payment TO ps17_order_invoice_payment_oryg; RENAME TABLE ps17_order_invoice_tax TO ps17_order_invoice_tax_oryg; RENAME TABLE ps17_order_message TO ps17_order_message_oryg; RENAME TABLE ps17_order_message_lang TO ps17_order_message_lang_oryg; RENAME TABLE ps17_order_payment TO ps17_order_payment_oryg; RENAME TABLE ps17_order_return TO ps17_order_return_oryg; RENAME TABLE ps17_order_return_detail TO ps17_order_return_detail_oryg; RENAME TABLE ps17_order_return_state TO ps17_order_return_state_oryg; RENAME TABLE ps17_order_return_state_lang TO ps17_order_return_state_lang_oryg; RENAME TABLE ps17_order_slip TO ps17_order_slip_oryg; RENAME TABLE ps17_order_slip_detail TO ps17_order_slip_detail_oryg; RENAME TABLE ps17_order_slip_detail_tax TO ps17_order_slip_detail_tax_oryg; RENAME TABLE ps17_order_state TO ps17_order_state_oryg; RENAME TABLE ps17_order_state_lang TO ps17_order_state_lang_oryg; e) Import exported earlier tables from PS 1.6 to PS 1.7 database. Just import. f) If you forgot to export / import one of above table from list at the beggining - at this point you will be reminded to RENAME TABLE ps_category TO ps17_category; RENAME TABLE ps_category_lang TO ps17_category_lang; RENAME TABLE ps_category_product TO ps17_category_product; RENAME TABLE ps_category_shop TO ps17_category_shop; RENAME TABLE ps_customer TO ps17_customer; RENAME TABLE ps_customer_group TO ps17_customer_group; RENAME TABLE ps_image_shop TO ps17_image_shop; RENAME TABLE ps_orders TO ps17_orders; RENAME TABLE ps_order_detail TO ps17_order_detail; RENAME TABLE ps_order_invoice TO ps17_order_invoice; RENAME TABLE ps_product TO ps17_product; RENAME TABLE ps_product_attribute TO ps17_product_attribute; RENAME TABLE ps_product_attribute_shop TO ps17_product_attribute_shop; RENAME TABLE ps_product_download TO ps17_product_download; RENAME TABLE ps_product_shop TO ps17_product_shop; RENAME TABLE ps_product_tag TO ps17_product_tag; RENAME TABLE ps_specific_price TO ps17_specific_price; RENAME TABLE ps_specific_price_priority TO ps17_specific_price_priority; RENAME TABLE ps_specific_price_rule TO ps17_specific_price_rule; RENAME TABLE ps_specific_price_rule_condition TO ps17_specific_price_rule_condition; RENAME TABLE ps_specific_price_rule_condition_group TO ps17_specific_price_rule_condition_group; RENAME TABLE ps_product_lang TO ps17_product_lang; RENAME TABLE ps_image TO ps17_image; RENAME TABLE ps_image_lang TO ps17_image_lang; RENAME TABLE ps_category_group TO ps17_category_group; RENAME TABLE ps_tag TO ps17_tag; RENAME TABLE ps_product_attribute_image TO ps17_product_attribute_image; RENAME TABLE ps_product_attribute_combination TO ps17_product_attribute_combination; RENAME TABLE ps_attribute TO ps17_attribute; RENAME TABLE ps_attribute_group TO ps17_attribute_group; RENAME TABLE ps_attribute_group_lang TO ps17_attribute_group_lang; RENAME TABLE ps_attribute_group_shop TO ps17_attribute_group_shop; RENAME TABLE ps_attribute_lang TO ps17_attribute_lang; RENAME TABLE ps_attribute_shop TO ps17_attribute_shop; RENAME TABLE ps_accessory TO ps17_accessory; RENAME TABLE ps_feature TO ps17_feature; RENAME TABLE ps_feature_lang TO ps17_feature_lang; RENAME TABLE ps_feature_product TO ps17_feature_product; RENAME TABLE ps_feature_shop TO ps17_feature_shop; RENAME TABLE ps_feature_value TO ps17_feature_value; RENAME TABLE ps_feature_value_lang TO ps17_feature_value_lang; RENAME TABLE ps_layered_product_attribute TO ps17_layered_product_attribute; RENAME TABLE ps_product_carrier TO ps17_product_carrier; RENAME TABLE ps_carrier TO ps17_carrier; RENAME TABLE ps_carrier_group TO ps17_carrier_group; RENAME TABLE ps_carrier_lang TO ps17_carrier_lang; RENAME TABLE ps_carrier_shop TO ps17_carrier_shop; RENAME TABLE ps_carrier_tax_rules_group_shop TO ps17_carrier_tax_rules_group_shop; RENAME TABLE ps_carrier_zone TO ps17_carrier_zone; RENAME TABLE ps_delivery TO ps17_delivery; RENAME TABLE ps_range_price TO ps17_range_price; RENAME TABLE ps_range_weight TO ps17_range_weight; RENAME TABLE ps_zone TO ps17_zone; RENAME TABLE ps_zone_shop TO ps17_zone_shop; RENAME TABLE ps_tax TO ps17_tax; RENAME TABLE ps_tax_lang TO ps17_tax_lang; RENAME TABLE ps_tax_rule TO ps17_tax_rule; RENAME TABLE ps_tax_rules_group TO ps17_tax_rules_group; RENAME TABLE ps_tax_rules_group_shop TO ps17_tax_rules_group_shop; RENAME TABLE ps_currency TO ps17_currency; RENAME TABLE ps_currency_shop TO ps17_currency_shop; RENAME TABLE ps_group TO ps17_group; RENAME TABLE ps_group_lang TO ps17_group_lang; RENAME TABLE ps_group_reduction TO ps17_group_reduction; RENAME TABLE ps_group_shop TO ps17_group_shop; RENAME TABLE ps_order_carrier TO ps17_order_carrier; RENAME TABLE ps_order_cart_rule TO ps17_order_cart_rule; RENAME TABLE ps_order_detail_tax TO ps17_order_detail_tax; RENAME TABLE ps_order_history TO ps17_order_history; RENAME TABLE ps_order_invoice_payment TO ps17_order_invoice_payment; RENAME TABLE ps_order_invoice_tax TO ps17_order_invoice_tax; RENAME TABLE ps_order_message TO ps17_order_message; RENAME TABLE ps_order_message_lang TO ps17_order_message_lang; RENAME TABLE ps_order_payment TO ps17_order_payment; RENAME TABLE ps_order_return TO ps17_order_return; RENAME TABLE ps_order_return_detail TO ps17_order_return_detail; RENAME TABLE ps_order_return_state TO ps17_order_return_state; RENAME TABLE ps_order_return_state_lang TO ps17_order_return_state_lang; RENAME TABLE ps_order_slip TO ps17_order_slip; RENAME TABLE ps_order_slip_detail TO ps17_order_slip_detail; RENAME TABLE ps_order_slip_detail_tax TO ps17_order_slip_detail_tax; RENAME TABLE ps_order_state TO ps17_order_state; RENAME TABLE ps_order_state_lang TO ps17_order_state_lang; RENAME TABLE ps_stock_available TO ps17_stock_available; My main ("home") category have ID 2. In my case I removed assign products to this category and leave connection to dipper category. But this is optional. It denepd on what you want to achaive. DELETE FROM ps17_category_product WHERE id_category=2; ....................................... g) Necessary changes in tables structure ALTER TABLE ps17_product ADD isbn varchar(13) DEFAULT NULL AFTER ean13; ALTER TABLE ps17_product ADD show_condition tinyint(1) NOT NULL DEFAULT '0' AFTER available_date; ALTER TABLE ps17_product ADD state int(11) unsigned NOT NULL DEFAULT '1'; ALTER TABLE ps17_product CHANGE id_product_redirected id_type_redirected int(10); ALTER TABLE ps17_product_shop ADD show_condition BOOLEAN NOT NULL DEFAULT FALSE AFTER available_date; ALTER TABLE ps17_product_shop CHANGE id_product_redirected id_type_redirected INT(10) UNSIGNED NOT NULL DEFAULT '0'; ALTER TABLE ps17_product_attribute ADD isbn VARCHAR(13) NOT NULL AFTER ean13; ALTER TABLE ps17_product_attribute_shop ADD id_product INT(10) UNSIGNED NOT NULL FIRST; ALTER TABLE ps17_product_download ADD UNIQUE(id_product); ALTER TABLE ps17_product_tag ADD id_lang INT(10) UNSIGNED NOT NULL AFTER id_tag; ALTER TABLE ps17_product_tag ADD KEY id_lang (id_lang, id_tag); ALTER TABLE ps17_specific_price ADD KEY id_product_attribute (id_product_attribute), ADD KEY id_shop (id_shop), ADD KEY id_customer(id_customer), ADD KEY `from` (`from`), ADD KEY `to` (`to`); ALTER TABLE ps17_specific_price ADD UNIQUE KEY id_product_2 (id_product,id_product_attribute,id_customer,id_cart,`from`,`to`,id_shop,id_shop_group,id_currency,id_country,id_group,from_quantity,id_specific_price_rule); ALTER TABLE ps17_image_shop ADD id_product INT(10) UNSIGNED NOT NULL FIRST; ALTER TABLE ps17_image_shop ADD PRIMARY KEY (id_image,id_shop); /* ADD UNIQUE KEY id_product (id_product,id_shop,cover); */ /* here we should add unique key, but in my case - I have duplicated entries and finally I didn't do that. */ ALTER TABLE ps17_category ADD KEY activenleft (active,nleft), ADD KEY activenright (active,nright); ALTER TABLE ps17_customer CHANGE passwd passwd VARCHAR(60) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL; ALTER TABLE ps17_customer ADD reset_password_token VARCHAR(40) NOT NULL AFTER date_upd, ADD reset_password_validity DATETIME NOT NULL AFTER reset_password_token; ALTER TABLE ps17_orders ADD round_type BOOLEAN NOT NULL DEFAULT TRUE AFTER round_mode; ALTER TABLE ps17_order_invoice ADD shop_address TEXT NOT NULL AFTER total_wrapping_tax_incl; ALTER TABLE ps17_order_invoice CHANGE total_discount_tax_excl total_discount_tax_excl DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_discount_tax_incl total_discount_tax_incl DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_paid_tax_excl total_paid_tax_excl DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_paid_tax_incl total_paid_tax_incl DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_products total_products DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_products_wt total_products_wt DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_shipping_tax_excl total_shipping_tax_excl DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_shipping_tax_incl total_shipping_tax_incl DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_wrapping_tax_excl total_wrapping_tax_excl DECIMAL(20,6) NOT NULL DEFAULT '0.00', CHANGE total_wrapping_tax_incl total_wrapping_tax_incl DECIMAL(20,6) NOT NULL DEFAULT '0.00'; ALTER TABLE ps17_order_detail ADD id_customization INT(10) UNSIGNED NOT NULL DEFAULT '0' AFTER product_attribute_id; ALTER TABLE ps17_order_detail ADD product_isbn VARCHAR(13) NOT NULL AFTER product_ean13; ALTER TABLE ps17_order_detail ADD original_wholesale_price DECIMAL(20,6) NOT NULL DEFAULT '0.000000' AFTER original_product_price; ALTER TABLE ps17_stock_available ADD physical_quantity INT(11) NOT NULL DEFAULT '0' AFTER quantity, ADD reserved_quantity INT(11) NOT NULL DEFAULT '0' AFTER physical_quantity; /* moving language information for tags to just added new column with language ID */ UPDATE ps17_product_tag pg LEFT JOIN ps17_tag t ON pg.id_tag=t.id_tag SET pg.id_lang=t.id_lang; /* rewriting product id's from table product_attribute to new column in table product_attribute_shop */ UPDATE ps17_product_attribute_shop pas LEFT JOIN ps17_product_attribute pa ON pa.id_product_attribute=pas.id_product_attribute SET pas.id_product=pa.id_product; /* only if your tax group id is different in new shop */ UPDATE ps17_carrier_tax_rules_group_shop SET id_tax_rules_group=1 WHERE id_tax_rules_group=6; UPDATE ps17_product SET id_tax_rules_group=1 WHERE id_tax_rules_group=6; UPDATE ps17_order_detail SET id_tax_rules_group=1 WHERE id_tax_rules_group=6; UPDATE ps17_tax_rule SET id_tax_rules_group=1 WHERE id_tax_rules_group=6; DELETE FROM ps17_tax_rules_group WHERE id_tax_rules_group=6; DELETE FROM ps17_tax_rules_group_shop WHERE id_tax_rules_group=6; UPDATE ps17_tax_rules_group SET deleted=0 WHERE id_tax_rules_group=1; ALTER TABLE ps17_currency DROP iso_code_num, DROP sign, DROP blank, DROP format, DROP decimals; ....................................... h) Update language settings After installing new localization pack (if you need it) check ID of this new language and comapre it with id of this language in your old Prestashop database. If this identifiers are different - you have to update it in tables listed below. In my case lang-id from PS 1.6 was 3 and just installed language-id in my new PS 1.7 was 7. _category_lang _product_lang _product_tag _tag _attribute_group_lang _attribute_lang _feature_lang _feature_value_lang _carrier_lang _tax_lang _group_lang _order_return_state_lang _order_state_lang UPDATE ps17_product_lang SET id_lang=7 WHERE id_lang=3; DELETE FROM ps17_category_lang WHERE id_lang!=1 AND id_lang!=3; UPDATE ps17_category_lang SET id_lang=7 WHERE id_lang=3; UPDATE ps17_product_tag SET id_lang=7 WHERE id_lang=3; UPDATE ps17_tag SET id_lang=7 WHERE id_lang=3; UPDATE ps17_attribute_group_lang SET id_lang=7 WHERE id_lang=3; UPDATE ps17_attribute_lang SET id_lang=7 WHERE id_lang=3; UPDATE ps17_feature_lang SET id_lang=7 WHERE id_lang=3; UPDATE ps17_feature_value_lang SET id_lang=7 WHERE id_lang=3; UPDATE ps17_carrier_lang SET id_lang=7 WHERE id_lang=3; UPDATE ps17_tax_lang SET id_lang=7 WHERE id_lang=3; DELETE FROM ps17_tax_lang WHERE id_lang!=1 AND id_lang!=3 AND id_lang!=7; /* I had in this table some redundant data. It's good accasion to remove them ;)' */ UPDATE ps17_group_lang SET id_lang=7 WHERE id_lang=3; UPDATE ps17_order_return_state_lang SET id_lang=7 WHERE id_lang=3; DELETE FROM ps17_order_return_state_lang WHERE id_lang!=1 AND id_lang!=3 AND id_lang!=7; /* I had in this table some redundant data. It's good accasion to remove them ;)' */ UPDATE ps17_order_state_lang SET id_lang=7 WHERE id_lang=3; DELETE FROM ps17_order_state_lang WHERE id_lang!=1 AND id_lang!=3 AND id_lang!=7; /* I had in this table some redundant data. It's good accasion to remove them ;)' */
  4. Nevermind... I realized after writing this post that I editing wrong file. I should edit (for example): /themes/classic/modules/contactform/views/templates/widget/contactform.tpl instead: /modules/contactform/views/templates/widget/contactform.tpl Sorry for confusion.
  5. Hi I try to do some changes in Classic theme in Prestashop 1.7.2. I try to do the same changes on localhost and on remote server. Result - the same. This are my test env for prestashop. I have disable cache option and forcing compilation. Also every time, many times, I used "clear cache" button in backoffice in Configure > Advanced parameters > Performance. It's very strange. When I edited some .tpl files I see changes at front. Like for example when I added map on my contact page below contact form. I modified file: /themes/classic/templates/contact.tpl and after refresing site I see changes. But... but when I change another tpl files, like for example: /modules/contactform/views/templates/widget/contactform.tpl I don't see any changes at front. In this example tpl file I removed first section of form - with subject select. Just because I convinced that selecting message subject have no sense and it's wrong from UX point of view.
  6. Hi I would likt to add something. This is complete polish (PL) translation of whole module. Regards psproductcountdown-pl.zip
  7. Hi How can I change definition of my last name on forum? I see this value when I enter to my profile but I can't change it. Why? How can I change my last name on forum?
  8. Category tree

    Answer to my own question... In my Prestashop I would like to have exapned all categories all the time. I'm starting with "Classic" theme. In file: /themes/classic/modules/ps_categorytree/views/templates/hook/ps_categorytree.tpl it's enugh to make two little changes. In two lines (line numer 39 and 50) which looks like this: <div class="collapse" id="exCollapsingNavbar{$node.id}"> add " in" to class atribute and add attribute "aria-expanded" with value "true". Final this two lines will look like this: <div class="collapse in" id="exCollapsingNavbar{$node.id}" aria-expanded="true"> That's all. Upload changed file.
  9. Category tree

    I was trying to use this code {if $node.id == $category.id} displaymytree{/if} in this file /themes/classic/modules/ps_categorytree/views/templates/hook/ps_categorytree.tpl but there is an error. I'm also don't know how/where to implement this change. Could you please give some advice? I have a feeling that if I would like to have mark selected category using some CSS class I have to use some code like above... Am I right? What I would like to acheive is to have by default expanded all categories and subcategories. I would like to have shown, expanded all categories all the time as I have now in PS 1.6 (my shop on PS 1.6: https://palmatum.pl ). Any advice? Now with this new PS 1.7 (not so new today...) I'm feel like years ago with OsCommerce - when I would like to have something - I have to code this by myself
  10. Tag cloud for prestashop 1.7.X

    I'm testing configuration of Prestashop 1.7 (axactly on 1.7.2.2 version). a) I've just installed blocktags module. First strange thing - after installing it - my layout configuration for index and product page changed from two columns version again to deafult full width option... hm Nevermind. I changed this again and it works. I assigned this module to hook displayLeftColumn. Why there is no option to assigned this module also to displayLeftColumnProduct hook? How to acheive this? c) A little funny... maybe it's solutions for someone who have problem with displaying this module at front At the begginig I thought that it not works because any tags appeard in my left column. I'm just testing raw Prestashop installation with oryginal demo data. And in default test products have no tags It's enough to add any in any product Maybe this help someone Thank you for adapting this module for PS 1.7!
  11. prestashop 1.7 show category list in footer

    Hi Swannb02 and Vekia, I tried first solution. I just added this block to footer as described. I done this on raw fresh PS 1.7.2 installation. It looks strange New line was added to footer with full toggle menu as it is on top. I don't know how to change layout of this categories embeded in footer. Now the easiest, the fastest solution is to add chosen (the most important fior me) categories manually using in backoffice this function: section Improve (PL: Ulepszenia) > menu Design (PL: Wygląd) > Link Widget It's enough. Maybe better solution when we have too much categories and we don't want to present all of them in footer. Regards!
  12. Disable caching back office

    El Patron, I asked my VPS administrator for info if something has changed last time on server etc. Generally nopthing has changed. Hu suggested that it could be transparent proxy-cache on internet provider side. I'm using Orange DSL. Maybe, but as I remember I thought about that and I checked values in back office on my mobile. But now I'm not sure if that was on WiFi or mobile connection. What else... at home last time I also totally can't access to my carrier website. Only using my cable internet connection. On every other connection (from exaple hotspot from my mobile) it works. Maybe it's the issue. bellini13, thank your for detailed describing situatiion. It could be reason, but not in my case, because from longer time I didn't change nothing in this cache options.
  13. Thanks guys I will check information about version 1.7 later If I will have some time I will prepare migration from 1.6.0 to 1.6.1 on different environment, maybe on another subdomain and I will check if it consume much time to set everything. Speed optimization is important. More and more, epsecially from SEO (Google SE) point of view
  14. Disable caching back office

    Thank you, but exactly my favourite browser is Firefox But... but what's interesting... I didn't change anything and now problem dissapeard. After making changes in products I see right now after it changes also in back office. Maybe server administrator change something for a while... I don't understand. We will see later.
  15. Is it worth to update Prestashop from 1.6.0.14 version to version 1.6.1.12 from March 2017? Especially thatit will be better in nearest future to update it to version 1.7? I mean the comparison of work on preparing update to results. In option of upgrading from 1.6.0 to 1.6.1 A little earlier I read many opinions about Prestashop 1.7 that this version have many defects, that's too early for update shop system for it and most of modules are not prepared for this version. From your experience... Is it already good moment to update PS to 1.7? Does all core functionailities works correctly in v1.7.0.6? To update or not to update...
×