Search the Community

Hi, I have just made an upgrade of development copy of my store via 1-Click upgrade from 1.6.1.20 (to 1.7.4.2). Currently I'm getting "Access denied" error when I try to open: Orders > Orders Discounts > Catalog Price Rules Customers > Customers Stats Shipping > Preferences International > Localization > Localization Shop Parameters > Order Settings > Order Settings Shop Parameters > Customer Settings > Titles Shop Parameters > Contact > Stores What coud be the problem? How to fix it?

Bonjour, Suite à la migration d'un prestashop de dernière version 1.6 vers la 1.7.8.5, je me retrouve (parfois) à avoir une erreur sur une commande. Ce n'est pas récurrent mais ça arrive de temps à autre (1 commande sur 5). J'ai un message vide qui se créer également dans l'onglet SAV. J'ai tenté de reproduire le bug mais je n'y arrive pas. Type error: Argument 2 passed to PrestaShop\PrestaShop\Core\Domain\Order\QueryResult\OrderMessageForViewing::__construct() must be of the type string, null given, called in /--privatefolder--/src/Adapter/Order/QueryHandler/GetOrderForViewingHandler.php on line 691 in src/Core/Domain/Order/QueryResult/OrderMessageForViewing.php (line 91) public function __construct( int $messageId, string $message, OrderMessageDateForViewing $messageDate, int $employeeId, bool $isCurrentEmployeesMessage, OrderMessageForViewing->__construct(0, null, object(OrderMessageDateForViewing), 0, false, null, null, '--PRENOM--', '--NOM--', false) in src/Adapter/Order/QueryHandler/GetOrderForViewingHandler.php (line 691) $isCurrentEmployeesMessage, $orderMessage['efirstname'], $orderMessage['elastname'], $orderMessage['cfirstname'], $orderMessage['clastname'], (bool)$orderMessage['private'] Problème lié à la ligne : $orderMessage['private'], donc lié au message. Je vous donne le maximum d'information que j'ai constater : l'erreur affecte seulement la commande en question lorsque je veux accéder au détail complet (lorsque l'on clique sur la commande). Sur le slide down aucun problème. Le client a écrit un message. Au niveau de l'horodatage, son message est avant le message vide suivi du message de validation de paiement (message automatique envoyé en privé). On parle en millième de secondes. Un message vide est créer dans l'onglet SAV et celui-ci est lié à la commande/client Solution provisoire trouvé qui enlève cette erreur : J'ai créer une ligne manuellement sur la BDD dans la table customer_message avec l'id du message vide qui est affiché dans le back office à l'onglet SAV. Avec ça, je n'ai plus l'erreur Je supprime directement le message vide dans l'ongle SAV. J'ai fait énormément de recherche sans trouver de solution. Beaucoup de solution sont lié à des adresses vides, etc.. j'ai tenté cette approche en mettant également à jour ma BDD mais rien n'y fait j'ai toujours ce problème. Ces topics sont identique à mon problème :

Hello, I'm Eric from Globo. Today I would like to share with you the 1-Click module. Overview Upgrade your store to the latest Prestashop version easier than ever in 1 click. Upgrade Prestashop 1.5 to 1.7, Upgrade Prestashop 1.6 to 1.7. What this module does for you ? You’re searching for a fast, easy, effective and secure tool to upgrade Prestashop to the latest version, this module is for you. Make it fast and easy to directly upgrade your store to the latest Prestashop version in one click Provide with full upgrade options such as backup files and database, upgrading default theme, keeping customized email templates, etc. Guarantee your store entirely secured, which is an integral factor when upgrading store Be able to check the changelog during and after the upgrade process Rollback to the previous Prestashop version in case you need Features 1-click upgrade Prestashop 1.5.x to 1.7 (latest version) 1-click upgrade Prestashop 1.6.x to 1.7 (latest version) 1-click upgrade Prestashop 1.5.x to 1.6 (latest version) 1-click upgrade Prestashop 1.7.x to 1.7 (latest version) 1-click upgrade Prestashop 1.5.x to 1.5 (latest version) 1-click upgrade Prestashop 1.6.x to 1.6 (latest version) Other features: Backup & restore Select Prestashop version that your store will be upgraded You can upgrade the default theme Option to decide upgrade email template. You can see the changelog of the upgrade process What your customers will like More happy and loyal customers visit your store thanks to smooth user experience with advanced functionality, which is the main core of your business development. Download the module: gautoupgradefree.zip

I need to manually update PS 1.7.0.1. I need some tutorial. It does not work 1-Click Upgrade. I get the following error: Error Javascript(parseJSON) detectado por acction..."upgradeFiles". Empezando la restauración... Screenshot: https://cl.ly/3E1p1q1Z0t2V

Hello all I know the wise men say, it's not the best idea to use the 1-click upgrade, but still... We are trying to update PS 1.7.6.7 to the newest version, but get the error after the files have been updated. And to the error we go: [INTERNAL] [URL]/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php line 168 - Symfony\Component\Config\Exception\FileLoaderLoadException: The file "[URL]/app/config/config.yml" does not contain valid YAML: Missing value for tag "php/const:PrestaShopBundle\Service\Form\MultistoreCheckboxEnabler::MULTISTORE_FIELD_PREFIX" at line 85 (near "multistore_field_prefix: !php/const:PrestaShopBundle\Service\Form\MultistoreCheckboxEnabler::MULTISTORE_FIELD_PREFIX") in [URL]/app/config/config.yml (which is being imported from "[URL]/app/config/config_prod.yml"). #0 [URL]/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(90): Symfony\Component\Config\Loader\FileLoader->doImport('/home/customer/...', NULL, false, '/home/customer/...') #1 [URL]/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(195): Symfony\Component\Config\Loader\FileLoader->import('config.yml', NULL, false, '/home/customer/...') #2 [URL]/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(127): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->parseImports(Array, '/home/customer/...') #3 [URL]/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/DelegatingLoader.php(40): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->load('/home/customer/...', NULL) #4 [URL]/app/AppKernel.php(150): Symfony\Component\Config\Loader\DelegatingLoader->load('/home/customer/...') #5 [URL]/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(776): AppKernel->registerContainerConfiguration(Object(Symfony\Component\Config\Loader\DelegatingLoader)) #6 [URL]/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(642): Symfony\Component\HttpKernel\Kernel->buildContainer() #7 [URL]/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(135): Symfony\Component\HttpKernel\Kernel->initializeContainer() #8 [URL]/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(74): Symfony\Component\HttpKernel\Kernel->boot() #9 [URL]/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader17.php(50): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initAppKernel() #10 [URL]/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(86): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader17->initConstants() #11 [URL]/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(41): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #12 [URL]/[ADMIN]/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #13 {main} The strangest thing is, that I managed to upgrade earlier this week, but not today. Can someone help me to tackle this error? Thank you in advance. Always getting goosebumps when upgrading PrestaShop: how on earth this can be so frustrating all the time...

Hola, Ha salido la versión 1 - Click upgrade versión 4.12.0 estable . EDITO este post el 08 de abril de 2021 para poner bien la versión estable voy a poner los pasos efectuados para poder actualizar desde la versión que tengas 1.7 a la 1.7.7.3 Hay que seguir estos pasos y lo voy a poner fácil y detallado todos los pasos. Vamos al detalle 1 - Ante todo copia de seguridad de los archivos y de la base de datos, de tu tienda en producción por si algo va mal ( este paso es obligatorio) 2 - Bajarse el 1 - Click Upgrade version 4.12.0 estable https://github.com/PrestaShop/autoupgrade/releases/download/v4.12.0/autoupgrade-v4.12.0.zip https://github.com/PrestaShop/autoupgrade/releases 3 - Entrar en el Back Office o el admin de la tienda 4 - Una vez dentro , ver la versión que tienes intalada, y así estar seguro para proceder a actualizar 5 - Asegurarte que no tienes el modulo 1 - click instalado en tu web y si lo tienes lo desactivas y lo desintalas 6 - Ahora subes el módulo que bajaste en el paso nº 2 de 1 - Click Upgrade versión 4.11.0 estable 7 - Te aseguras de que pone la versión que tienes y la que te va a actualizar 8 - Pones la tienda en mantenimiento y luego le das al botón de comprobar actualización ( esto es obligatorio) , si no lo haces te puede fallar lo demás 9 - Ahora ya viene lo bueno , Click al botón de actualizar a prestashop pone 1.7.4.2 y se actualizara a 1.7.4.2 , ya lo verás 10 - No te asustes, si sale error , espera hasta que termine 11 - Ahora ya esta todo instalado, ( Atención con los siguientes pasos son importantes) 12 - Ir a Módulos , para desinstalar el 1- Click Upgrade 4.0.0 beta 5 , verás que te deslogueas y pierdes los estilos ( no asustarse, es normal) en el siguiente paso se arregla 13 - Ahora esta sin estilos , entra en el admin , y una vez dentro (Saldrá el menu en color azul y feo ) lo arreglamos dando click a Modo mantenimiento y activando la tienda 14 - Ir a Módulos , para desinstalar el 1- Click Upgrade 4.0.0 beta 5 , Desactivar y luego desinstalar ( paso obligatorio ) 15 - Cerrar sesión y volver a entrar , ahora el back office la pantalla del login del admin ya sale correcta. 16 - Una vez dentro , debería salirte bien, pero si te sale azul el menu lateral, refrescas el navegador con las teclas Ctrl + F5 y ahora ya sale bien 17 - Borra el caché de la tienda , en Parámetros Avanzados / Rendimiento arriba botón Borrar caché 18 - Prueba la tienda que todo te funciona bien y correctamente la version 1.7.4.2 que acabas de actualizar 18 - Recuerda la copia que hizo el modulo 1 - click upgrade 4.11.0 estable , parece que ahora sirve 19 - Si te falla, debes volver con las copias de seguridad tuyas, ¿Recuerdas? las que hiciste en el paso 1 , y eran obligatorias VER IMAGENES: 4 - Una vez dentro , ver la versión que tienes intalada, y así estar seguro para proceder a actualizar 6 - Ahora subes el módulo que bajaste en el paso nº 2 de 1 - Click Upgrade vesión 4.0.0 beta 5 7 - Te aseguras de que pone la versión que tienes y la que te va a actualizar 8 - Pones la tienda en mantenimiento y luego le das al botón de comprobar actualización ( esto es obligatorio) , si no lo haces te puede fallar lo demás 9 - Ahora ya biene lo bueno , Click al botón de actualizar a prestashop pone 1.7.4.2 y se actualizara a 1.7.4.2 , ya lo verás 11 - Ahora ya esta todo instalado, ( Atención con los siguientes pasos son importantes) 14 - Ir a Módulos , para desinstalar el 1- Click Upgrade 4.0.0 beta 5 , Desactivar y luego desintalar ( paso obligatorio ) 18 - Prueba la tienda que todo te funciona bien y correctamente la version 1.7.4.2 que acabas de actualizar Saludos

Bonjour, Boutique en production sous 1.7.4.2 j'ai essayé de mettre à jour via le module 1-Click Upgrade (à jour) et j'ai reçu ce message d'erreur : "Erreur Javascript (parse JSON) détecté pour l'actionupgradeModules" accompagné de : SQL 1.7.7.0 1146 in ALTER TABLE `ps_connections` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci: Table 'db745838102.ps_connections' doesn't exist SQL 1.7.7.0 1146 in ALTER TABLE `ps_connections_page` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci: Table 'db745838102.ps_connections_page' doesn't exist SQL 1.7.7.0 1146 in ALTER TABLE `ps_connections_source` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci: Table 'db745838102.ps_connections_source' doesn't exist SQL 1.7.7.0 1146 in ALTER TABLE `ps_guest` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci: Table 'db745838102.ps_guest' doesn't exist SQL 1.7.7.0 1146 in ALTER TABLE `ps_statssearch` CHANGE `keywords` `keywords` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL: Table 'db745838102.ps_statssearch' doesn't exist SQL 1.7.7.0 1146 in ALTER TABLE `ps_connections` CHANGE `http_referer` `http_referer` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL: Table 'db745838102.ps_connections' doesn't exist Si quelqu'un a une piste bonne journée.

Bonjour, Alors voici mon problème, je souhaiterais mettre à jour ma boutique (v 1.6.1.18) en passant par le module 1-click upgrade mais voilà impossible de l'installer. Lorsque je clique sur le bouton "installer" dans la rubrique "modules" de mon BO voilà ce qui est écrit à l'écran : [PrestaShop] Fatal error in module file :/home/www/vap-access/prod/modules/autoupgrade/autoupgrade.php: syntax error, unexpected '[', expecting ')' Ensuite impossible d'afficher le BO et évidemment en supprimant le dossier du module via FTP ça refonctionne ^^ Merci d'avance pour vos idées :)

Version de PS : 1.7.6.7 Thème (défaut/perso) : Classic (modifié) Hébergement : OVH Version de PHP : 7.3 Bonjour, souhaitant mettre ma boutique 1.7.6.7 à jour vers la version proposé par le module natif "1-Click Upgrade" (1.7.6.8) je me suis assuré que les points de la liste de vérifications soient au vert (sauf les deux derniers qui sont avec un triangle jaunâtre dont le statut peut être ignoré) j'ai donc 8 points de la liste qui sont en vert sur les 10 (boutique mise en maintenance et cache désactivé). Your current PrestaShop version: 1.7.6.7 Latest official version for minor channel.: 1.7.6 stable - (1.7.6.8) - Dernière vérification : 2020-10-16 19:00:27 Je clique sur "VERIFIER SI UNE NOUVELLE VERSION EST DISPONIBLE" ça détecte bien une nouvelle version puis plus rien. Le bouton interactif qui permet la mise a jour ne pointe pas le bout de son nez.. J'avais réussi la maj de 1.7.6.5 vers 1.7.6.7, mais là ça veut pas. Savez vous que faire ?

Hi I'm investigating the option of 1-click upgrade. Apache/2.2.22 (Debian) PHP Version 5.6.6 PS 1.6.1.13 1-click upgrade v4.10.1 the shop 1.6.1.13 has a bug, where price go negative, if product has specific prices at bigger amount sale (though if the product has specific price per combination it works fine) I read somewhere that this bug was taken care of in 1.6.1.17+ or something, and thought of upgrading to the latest 1.6 version. (.24) However - 1-click gives me this info: The PHP version your server is running on is obsolete and needs to be upgraded. Learn more why or ignore. (but link to Learn more why is broken so I can't see what or if it's ok if I ignore? PHP's max_execution_time setting has a high value or is disabled entirely (current value: 1000 seconds) - what should it be, then? START YOUR UPGRADE [Green v icon] Congratulations, you are already using the latest version available! Is it talking about PS version? 'cause that is not the latest version? Your current PrestaShop version: 1.6.1.13 Latest official version for archive channel.: N/A I am confused about these info's - and if I should continue this procedure - but what are my alternative? Can anyone guide me to the best way to make this minor update? Thank you for your precious time It's valuable.

Hello, I'm running into issues by doing 1-click upgrade of Prestashop 1.7.x on shared webhosting (WEDOS, Czech Republic). It works all fine, but one of the last steps is to upgrade /admin/.htaccess file, which includes rule on line 17 Options -MultiViews This rule is banned at WEDOS webhosting and produces error 500, which causes upgrade to fail. I wasn't able to skip this .htaccess upgrade, file premissions didn't help. I believe it would all run very smoothly with this one file skipped from the upgrade process, is there any way of editing list of files to upgrade? Did anyone have this solved? Thank you very much!

Hello, I'm trying to upgrade from 1.7.5.2 to 1.7.6 using 1-Click Upgrade. Checklist is OK. This error message keeps showing and clicking on the upgrade button makes no effect. Permissions in admin/autoupgrade are all set to 755 for folders and 644 for files. I'm obviously missing something, can anyone help? Thank you.

Hi everybody, I've searched in the forum but nothing seems to match my issue. When I click on 1-click upgrade's "Configure" button on PS 1.6.1.16 it's weeks I get a timeout and can not access the page which is a big problem as I now wish to upgrade to PS 1.7.5.1 and can't. Any hint on how to check what's causing the timeout? In some forum's topics I read a problem could be the addons marketplace connection so I also signed out from BO and the connection is off but no changes unfortunately. Any help much appreciated, thank you very much for reading

Hello, I can't upgrade my PS version 1.7.4 to 1.7.6 because when I use the Upgrade module, I've an error message with a 504 "backend unavailable". What's the problem? Thanks for your help. I try under safari and Chrome My Php is PHP 7.3

Hi, Can someone help me to keep my current modified default-bootstrap theme from v1.6 and migrate my store to new v1.7 without any error? I try to export my theme and upload it to new v1.7 but it shows not for this version! And when I migrate my store using 1-click migration by unselecting the update theme option it shows 500 Server error! I try to fix it by removing default-bootstrap theme folder from the theme directory and replace it with classic theme! Now my backend is accessible but all got messy please check that in attachment! *************Logs************** *ERROR* v1.7.5.2 2019/06/01 - 09:57:18: [ThemeRepository] Theme configuration file not found for theme at `C:\Program Files (x86)\Ampps\www\p/themes/classic/config/theme.yml`. at line 144 in file src/Core/Addon/Theme/ThemeRepository.php *ERROR* v1.7.5.2 2019/06/01 - 10:17:57: [ThemeRepository] Theme configuration file not found for theme at `C:\Program Files (x86)\Ampps\www\p/themes/classic/config/theme.yml`. at line 144 in file src/Core/Addon/Theme/ThemeRepository.php *ERROR* v1.7.5.2 2019/06/01 - 10:18:05: [ThemeRepository] Theme configuration file not found for theme at `C:\Program Files (x86)\Ampps\www\p/themes/classic/config/theme.yml`. at line 144 in file src/Core/Addon/Theme/ThemeRepository.php *ERROR* v1.7.5.2 2019/06/01 - 10:18:09: [ThemeRepository] Theme configuration file not found for theme at `C:\Program Files (x86)\Ampps\www\p/themes/classic/config/theme.yml`. at line 144 in file src/Core/Addon/Theme/ThemeRepository.php *ERROR* v1.7.5.2 2019/06/01 - 10:20:28: [ThemeRepository] Theme configuration file not found for theme at `C:\Program Files (x86)\Ampps\www\p/themes/classic/config/theme.yml`. at line 144 in file src/Core/Addon/Theme/ThemeRepository.php **********End Logs**************

Brand new test store Click 1 click upgrade installation. Success message Module(s) installed successfully followed by failure message You do not have permission to configure this module. Modules directory contains autoupgrade folder dated today. Modules list in admin offers 1-click upgrade as available to be installed. Click install again, same results as above. Also tried installing via prestashop download. Same results.

Bonjour, J'ai une boutique actuellement en version 1.7.0.3 que je souhaiterais mettre à jour vers la dernière version stable, 1.7.2.2. Quand je lance la mise à jour depuis le module 1-click Upgrade, la dernière version se télécharge bien comme il faut. J'ai toutefois une erreur qui me dit que le nom du backup n'a pas été renseigné. N'ayant pas trouvé où renseigner cette information, j'ai désactivé l'option "Back up my files and database" et relancé la mise à jour (j'ai fait une sauvegarde manuelle de tout ça). Ça m'annonce que 17152 fichiers doivent être modifiés, alors que la comparaison de version ne mentionne que 5157 fichiers à modifier et 895 à supprimer. De plus, la mise à jour reste bloquée à 17152 fichiers indéfiniment, jusqu'à ce que j'ai la fameuse erreur [Ajax / Server Error for action upgradeFiles] textStatus: "error " errorThrown:" " jqXHR: " " En cherchant une solution, j'ai voulu passer par l'installation via le répertoire local, en changeant cette option dans le mode expert du module 1-click Upgrade. Seulement, quand je sauvegarde mon choix, celui-ci n'est pas pris en compte et quand je lance la mise à jour, ça télécharge à nouveau la dernière version depuis Prestashop au lieu de se baser sur le répertoire local (l'option dans le mode expert reste sur "version majeure", même cas de figure quand je passe sur "version mineure"). Avez-vous une idée de la nature du problème ? Merci d'avance !

Zdravo, Rad bi nadgradil verzijo PS 1.6.1.18 na zadnjo (PS 1.6.1.22) ... modul 1-Click Upgrade mi ponudi upgrade na zadnjo verzijo 1.7.xxx in ne znam spremeniti verzijo. Ima kdo navodila ali video? ... 1-Click modul nima navodil in tehnična pomoč ne odgovarja hvala

Hey guys I installed: 1 click upgrade v.4.0 beta module to upgrade my site to prestashop 1.7.4.0. I downloaded the module from here: https://github.com/PrestaShop/autoupgrade/releases/tag/v4.0.0-beta.3 Then I installed the module successfully. After tryint to use the module to upgrade my site to Prestashop 1.7.4.0. It gives me this error: [INTERNAL] C:\Bitnami\prestashop-1.7.3.4-0\apps\prestashop\htdocs\modules\autoupgrade\classes\Tools14.php line 1399 - Allowed memory size of 134217728 bytes exhausted (tried to allocate 65011736 bytes) Now I've tried changing, memory_limit sizes and memory upload sizes inside prestashop and in bitnami itself to 512M then restarted MySQL and Apache, cleaned my browser cache. THen trying it again. But it still is giving me that error.

Hola, mi tienda está funcionando y quisiera actualizarla a la siguiente versión estable 1.7.5.0 Cuando lo intento desde el módulo 1-Click Upgrade v4.5.1 todo va bien hasta que llega a los pocos minutos el mensaje 'Connection Timeout'. Leyendo otros problemas similares modifiqué y aumenté el valor de max_execution_time, max_input_vars, memory_limits sin éxito. Alguien pasó por lo mismo? Tienen idea de qué puede ser? o es que el módulo no está funcionando correctamente. Aguardo sus comentarios y gracias.

Bonjour, je souhaitais mettre à jour ma boutique Your current PrestaShop version 1.6.1.16 Latest official version for major channel. 1.7.4 stable (1.7.4.2) via le module 1-Click Upgrade mais j'ai le message d'erreur suivant à la fin [ERROR] /homepages/16/d649899425/htdocs/NEWSSDBDV/admin456bwfb9v/autoupgrade/latest/prestashop does not exist or is not a directory. Ca parle a quelqu'un et quelle est la solution ? merci de votre aide

Hi, We get the following error trying to login to backend of our website, after trying a 1-click upgrade to 1.7.4.4 from local directory. Page is in Maintenance mode. URL: ma-nordic.dk. Please help! FatalErrorException in AdminLoginController.php line 394: Compile Error: Declaration of AdminLoginControllerCore::viewAccess() must be compatible with AdminControllerCore::viewAccess($disable = false)

Hola, he intentado actualizar de 1.7.3.2 a 1.7.4.2 mediante el módulo 1-click upgrade y todo iba bien hasta que apareció error:Error during database upgrade. You may need to restore your database.Error upgrading Doctrine schemaPara más detalles os pego lo siguiente:Migrating old setting file...parameters file already exists!Finished... [OK] SQL 1.7.3.0 SET SESSION sql_mode = ''[OK] SQL 1.7.3.0 SET NAMES 'utf8'[OK] SQL 1.7.3.0 UPDATE `sps_tab` SET `position` = 0 WHERE `class_name` = 'AdminZones' AND `position` = '1'[OK] SQL 1.7.3.0 UPDATE `sps_tab` SET `position` = 1 WHERE `class_name` = 'AdminCountries' AND `position` = '0'[OK] PHP 1.7.3.0 : /* PHP:ps_1730_add_quick_access_evaluation_catalog(); */[OK] PHP 1.7.3.0 : /* PHP:ps_1730_move_some_aeuc_configuration_to_core(); */[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product` ADD `low_stock_threshold` INT(10) NULL DEFAULT NULL AFTER `minimal_quantity`: Duplicate column name 'low_stock_threshold'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product` ADD `additional_delivery_times` tinyint(1) unsigned NOT NULL DEFAULT '1' AFTER `out_of_stock`: Duplicate column name 'additional_delivery_times'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product_lang` ADD `delivery_in_stock` varchar(255) DEFAULT NULL: Duplicate column name 'delivery_in_stock'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product_lang` ADD `delivery_out_stock` varchar(255) DEFAULT NULL: Duplicate column name 'delivery_out_stock'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product_shop` ADD `low_stock_threshold` INT(10) NULL DEFAULT NULL AFTER `minimal_quantity`: Duplicate column name 'low_stock_threshold'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product_attribute` ADD `low_stock_threshold` INT(10) NULL DEFAULT NULL AFTER `minimal_quantity`: Duplicate column name 'low_stock_threshold'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product_attribute_shop` ADD `low_stock_threshold` INT(10) NULL DEFAULT NULL AFTER `minimal_quantity`: Duplicate column name 'low_stock_threshold'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product` ADD `low_stock_alert` TINYINT(1) NOT NULL DEFAULT 0 AFTER `low_stock_threshold`: Duplicate column name 'low_stock_alert'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product_shop` ADD `low_stock_alert` TINYINT(1) NOT NULL DEFAULT 0 AFTER `low_stock_threshold`: Duplicate column name 'low_stock_alert'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product_attribute` ADD `low_stock_alert` TINYINT(1) NOT NULL DEFAULT 0 AFTER `low_stock_threshold`: Duplicate column name 'low_stock_alert'[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_product_attribute_shop` ADD `low_stock_alert` TINYINT(1) NOT NULL DEFAULT 0 AFTER `low_stock_threshold`: Duplicate column name 'low_stock_alert'[DROP] SQL `sps_store_lang` table has been dropped.[OK] SQL 1.7.3.0 CREATE TABLE IF NOT EXISTS `sps_store_lang` ( `id_store` int(11) unsigned NOT NULL, `id_lang` int(11) unsigned NOT NULL, `name` varchar(255) NOT NULL, `address1` varchar(255) NOT NULL, `address2` varchar(255) DEFAULT NULL, `hours` text, `note` text, PRIMARY KEY (`id_store`, `id_lang`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8[OK] PHP 1.7.3.0 : /* PHP:ps_1730_migrate_data_from_store_to_store_lang_and_clean_store(); */[WARNING] SQL 1.7.3.0 1091 in ALTER TABLE `sps_store` DROP `name`, DROP `address1`, DROP `address2`, DROP `hours`, DROP `note`: Can't DROP 'name'; check that column/key exists[OK] SQL 1.7.3.0 ALTER TABLE `sps_feature_product` DROP PRIMARY KEY, ADD PRIMARY KEY (`id_feature`, `id_product`, `id_feature_value`)[WARNING] SQL 1.7.3.0 1060 in ALTER TABLE `sps_customization_field` ADD `is_deleted` TINYINT(1) NOT NULL DEFAULT '0': Duplicate column name 'is_deleted'[OK] SQL 1.7.3.0 INSERT IGNORE INTO `sps_hook` (`id_hook`, `name`, `title`, `description`, `position`) VALUES (NULL, 'displayAdminCustomersAddressesItemAction', 'Display new elements in the Back Office, tab AdminCustomers, Addresses actions', 'This hook launches modules when the Addresses list into the AdminCustomers tab is displayed in the Back Office', '1'), (NULL, 'displayDashboardToolbarTopMenu', 'Display new elements in back office page with a dashboard, on top Menu', 'This hook launches modules when a page with a dashboard is displayed', '1'), (NULL, 'displayDashboardToolbarIcons', 'Display new elements in back office page with dashboard, on icons list', 'This hook launches modules when the back office with dashboard is displayed', '1')[OK] SQL 1.7.3.0 INSERT IGNORE INTO `sps_authorization_role` (`slug`) VALUES ('ROLE_MOD_TAB_DEFAULT_CREATE'), ('ROLE_MOD_TAB_DEFAULT_READ'), ('ROLE_MOD_TAB_DEFAULT_UPDATE'), ('ROLE_MOD_TAB_DEFAULT_DELETE')[OK] SQL 1.7.4.0 SET SESSION sql_mode = ''[OK] SQL 1.7.4.0 SET NAMES 'utf8'[OK] SQL 1.7.4.0 ALTER TABLE `sps_order_detail` DROP KEY product_id, ADD KEY product_id (product_id, product_attribute_id)[OK] SQL 1.7.4.0 INSERT IGNORE INTO `sps_hook` (`id_hook`, `name`, `title`, `description`, `position`) VALUES (NULL, 'actionAdministrationPageForm', 'Manage Administration Page form fields', 'This hook adds, update or remove fields of the Administration Page form', '1'), (NULL, 'actionAdministrationPageFormSave', 'Processing Administration page form', 'This hook is called when the Administration Page form is processed', '1'), (NULL, 'actionPerformancePageForm', 'Manage Performance Page form fields', 'This hook adds, update or remove fields of the Performance Page form', '1'), (NULL, 'actionPerformancePageFormSave', 'Processing Performance page form', 'This hook is called when the Performance Page form is processed', '1'), (NULL, 'actionMaintenancePageForm', 'Manage Maintenance Page form fields', 'This hook adds, update or remove fields of the Maintenance Page form', '1'), (NULL, 'actionMaintenancePageFormSave', 'Processing Maintenance page form', 'This hook is called when the Maintenance Page form is processed', '1'), (NULL, 'displayAdminEndContent', 'Administration end of content', 'This hook is displayed at the end of the main content, before the footer', '1')[OK] PHP 1.7.4.0 : /* PHP:ps_1740_update_module_tabs(); */[OK] SQL 1.7.4.1 SET SESSION sql_mode = ''[OK] SQL 1.7.4.1 SET NAMES 'utf8'[OK] SQL 1.7.4.1 ALTER TABLE `sps_cart_rule` ADD KEY `date_from` (`date_from`), ADD KEY `date_to` (`date_to`)[OK] SQL 1.7.4.2 SET SESSION sql_mode = ''[OK] SQL 1.7.4.2 SET NAMES 'utf8'[OK] SQL 1.7.4.2 UPDATE `sps_employee` SET `bo_css` = "theme.css"Updating database schema...16:32:27 ERROR [console] Error thrown while running command "prestashop:schema:update-without-foreign". Message: "Unknown database type bit requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it." ["exception" => Doctrine\DBAL\DBALException { …},"command" => "prestashop:schema:update-without-foreign","message" => "Unknown database type bit requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it."] []In AbstractPlatform.php line 423:Unknown database type bit requested, Doctrine\DBAL\Platforms\MySqlPlatformmay not support it.prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--]

Hola a todos, estoy teniendo problemas para actualizar mi tienda de Prestashop, al intentar actualizarla me da este error. Alguien me dice como puedo solucionarlo? Gracias de antemano.

Hola, Estoy intentando actualizar prestashop 1.7 con el modulo 1-Click Upgrade, pero me arroja el error "Unable to check md5 files" Ya cambien todos los directorios y archivos a 755 y 644, pero sigue con ese error. Llevo tiempo dándole al problema sin poder solucionarlo. Espero puedan ayudarme. Saludos, RO.