Cap'tain Caverne Posted December 29, 2010 Share Posted December 29, 2010 Bonjour à toutes et à tous,Suite à mise à jour, de la version 1.3.1.1 à la version 1.3.2.3, des erreur SQL sont apparue à la fin de la procédure.Ne connaissant pas ce type de message, je débute avec Prestashop, je demande votre aide pour savoir si ces messages sont importants ou pas, ou si c'est juste des messages de colonne, tables ou autres ayant déjà la mise à jour de faite.Merci d'avance, voici les messages : v1.3.1.1 -> v1.3.2.3SET NAMES 'utf8'SET NAMES 'utf8'ALTER TABLE `pss_order_detail` ADD `reduction_percent` DECIMAL(10, 2) NOT NULL AFTER `product_price`(1060) Duplicate column name 'reduction_percent'ALTER TABLE `pss_order_detail` ADD `reduction_amount` DECIMAL(20, 6) NOT NULL AFTER `reduction_percent`(1060) Duplicate column name 'reduction_amount'ALTER TABLE `pss_country` CHANGE `need_identification_number` `need_identification_number` TINYINT(1) NOT NULL DEFAULT '0'INSERT INTO `pss_configuration` (`name`, `value`, `date_add`, `date_upd`) VALUES ('PS_1_3_2_UPDATE_DATE', NOW(), NOW(), NOW())(1062) Duplicate entry 'PS_1_3_2_UPDATE_DATE' for key 2ALTER TABLE `pss_search_index` CHANGE `weight` `weight` SMALLINT(4) unsigned NOT NULL DEFAULT '1'ALTER TABLE `pss_image` DROP INDEX `product_position`, ADD UNIQUE `product_position` (`id_product`, `position`)ALTER TABLE `pss_zone` DROP `enabled`(1091) Can't DROP 'enabled'; check that column/key existsSET @id_hook = (SELECT id_hook FROM pss_hook WHERE name = 'backOfficeHeader')SET @position = (SELECT IFNULL(MAX(position),0)+1 FROM pss_hook_module WHERE id_hook = @id_hook)INSERT IGNORE INTO pss_hook_module (id_hook, id_module, position) VALUES (@id_hook, (SELECT id_module FROM pss_module WHERE name = 'statsbestcustomers'), @position)SET @position = @position + 1INSERT IGNORE INTO pss_hook_module (id_hook, id_module, position) VALUES (@id_hook, (SELECT id_module FROM pss_module WHERE name = 'statsbestproducts'), @position)SET @position = @position + 1INSERT IGNORE INTO pss_hook_module (id_hook, id_module, position) VALUES (@id_hook, (SELECT id_module FROM pss_module WHERE name = 'statsbestvouchers'), @position)SET @position = @position + 1INSERT IGNORE INTO pss_hook_module (id_hook, id_module, position) VALUES (@id_hook, (SELECT id_module FROM pss_module WHERE name = 'statsbestcategories'), @position)SET @position = @position + 1INSERT IGNORE INTO pss_hook_module (id_hook, id_module, position) VALUES (@id_hook, (SELECT id_module FROM pss_module WHERE name = 'statsbestcarriers'), @position)SET NAMES 'utf8'===================================================v1.3.2.3 -> v1.3.3.0SET NAMES 'utf8'ALTER TABLE `pss_order_detail` ADD `group_reduction` DECIMAL(10, 2) NOT NULL AFTER `reduction_amount`(1060) Duplicate column name 'group_reduction'ALTER TABLE `pss_order_detail` ADD `ecotax_tax_rate` DECIMAL(5, 3) NOT NULL AFTER `ecotax`(1060) Duplicate column name 'ecotax_tax_rate'ALTER TABLE `pss_product` CHANGE `ecotax` `ecotax` DECIMAL(21, 6) NOT NULL DEFAULT '0.00'INSERT INTO `pss_configuration` (`name`, `value`, `date_add`, `date_upd`) SELECT 'PS_LOCALE_LANGUAGE', l.`iso_code`, NOW(), NOW() FROM `pss_configuration` c INNER JOIN `pss_lang` l ON (l.`id_lang` = c.`value`) WHERE c.`name` = 'PS_LANG_DEFAULT'(1062) Duplicate entry 'PS_LOCALE_LANGUAGE' for key 2INSERT INTO `pss_configuration` (`name`, `value`, `date_add`, `date_upd`) SELECT 'PS_LOCALE_COUNTRY', co.`iso_code`, NOW(), NOW() FROM `pss_configuration` c INNER JOIN `pss_country` co ON (co.`id_country` = c.`value`) WHERE c.`name` = 'PS_COUNTRY_DEFAULT'(1062) Duplicate entry 'PS_LOCALE_COUNTRY' for key 2===================================================v1.3.3.0 -> v1.3.4.0SET NAMES 'utf8'===================================================v1.3.4.0 -> v1.3.5.0SET NAMES 'utf8' De plus, suite à ces mises à jour sucessives, et ces erreurs, certaines descriptions de produits sont HS, sans aucune modifications de mes fichiers CSS, et avec le thème de base.Je suis passer progressivement de la 1.3.1.1 stable et sans bugs d'affichage avant la mise à jour, à la 1.3.5.0, mais ça ne règle pas le problème des descriptions HS.Merci pour vos futures réponses. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now