Search the Community

Hola , Alguien ha pasado por esto , que me pueda ayudar a solucionarlo? , quiero actualizar la tienda , actualmente tengo la versión 1.7.5.0 ; instale y tengo la última versión de 1-Click Upgrade (4.7.0) pero al querer actualizar , me marca el siguiente error : Error: Unable to check md5 files he leído en algunos foros que dice que se soluciona cambiando los permisos de las carpetas y los archivos de 777 a 755 y de 666 a 644, lo he hecho , pero no se ha ido el error . muchas gracias de antemano.

XML, CSV and API integration for PrestaShop Automate the flow of your product catalog This module allow you integrate your PrestaShop store with any numbers of API, XML and CSV feeds. Module connect to local or remote XML and CSV files and APIs and read data from them. Select the data you want to transfer to your store and run the import. No limits for XML, CSV and API integrations Run with large files with 20.000 and more product or combinations The functionality of the module reflects the needs of our customers (over 300 module updates in last years) and allow PrestaShop Admin to create import schema for any sales scenario. More info and module demo: https://prestashow.com/en/prestashop-modules/5-prestashop-smart-importer-xml-csv-api-integration.html PrestaShop: 1.6, 1.7, 8.x Available Translations: EN, PL, IT, ES, FR, DE PrestaShop Multistore and Advanced Stock Management Support 1-click updates and support included The module guide you through the process of adding and configuring new XML, CSV or API in 5 easy steps. The module supports all PrestaShop catalog fields that you can configure for import and update data. You can modify the configuration for each integration and each field to add, skip or modify products before they hit the store. It's up to you to select the data to import or update. If you have any questions - go ahead 🙂 Screenshots: 1. Integrations list 2. Data matching: from feed to PrerstaShop: 3. Importing / updating: one by one of fully automatic:

Hello, When I do a fresh installation of Prestashop 8.1.1, in the advanced parameters section, the New and Experimental Features page, in addition to the 2 New Features (New product page and various image formats), also displays the 12 Experimental Features to enable or disable. In the case of updating a PrestaShop store from 1.7.8.9 to 8.1.1, only the 2 new features appear and none of the 12 experimental features to activate or deactivate appears. What is the reason and how can I have this option in case of upgrading from Prestashop 1.7.8.9 to 8.1.1? The update is done through the standard Prestashop 1-Click upgrade module. Thanks

I have a products category in my cart that is subject to a specific minimum order quantity rules; when I update the quantity, the cart modal goes into a loop and only by reloading is the set quantity updated; the error is: errors: [,…] 0: "error_text" hasError: true id_product: "id" id_product_attribute: "0" linkAction: "test" modal: false quantity: 100 success: false Anyone can help me please? THANKS!

Salve, come purtroppo capita di consueto, durante un'ennesima migrazione da un PS 1.6 ad una nuova installazione 1.7(.8.7), qualcosa deve essere andato storto. Non mi fa accedere ai moduli se non in debug, l'errore è questo (scusate per le censure ma è il sito di un cliente): Compile Error: require_once(): Failed opening required '/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/home/modules/statsforecast/statsforecast.php' (include_path='/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/vendor/pear/pear_exception:/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/vendor/pear/console_getopt:/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/vendor/pear/pear-core-minimal/src:/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/vendor/pear/archive_tar:.:/opt/plesk/php/7.4/share/pear') [Symfony\Component\Debug\Exception\FatalErrorException 0] Andando per tantivi, ho provato ad eludere la cartella del modulo in FTP indicato nella prima riga del log, ma me ne mostra sempre un altro, sono arrivato ad eludere circa dieci moduli quindi penso che il problema sia legato a PS in sè; ho provato a cambiare versioni del PHP ma è sempre uguale; ho provato a pulire cache sia automaticamente che manualmente; ho provato ad aggiornare tutti i moduli che mi segnalava da aggiornare giusto per; Vedo che il problema riguarda la cartella /vendor/pear/ ma non capisco il motivo. Aggiungo che la migrazione era stata fatta in una sottocartella temporanea, poi ho sposato tutti i file nella root e adattato il db (rimuovendo tutte le stringe che richiamavano la vecchia cartella). Se attivo il debug funziona correttamente; il resto dell'admin ed il front funziona correttamente. Se qualcuno sa indicarmi ringrazio in anticipo

I have a question about the Cookie key and the question of password generation of the platform. 1. I currently have version 1.6.0.14, now I am upgrading to version 1.7.2.4, in a new installation / host, I know that a new key to the cookie is generated when installing this new installation, I wonder if there is any way to update the passwords of all clients according to this new cookie and not use the cookie of the old version? And if I want to change the cookie manually, is there any way to regenerate the passwords arranged in the database? I am doomed to always use the same cookie key? 2. Given the same scenario Store 1.6.0.14, the database has more than 50,000 registered customers, where the chosen encryption passwords is Rijndael with mcrypt library, the question is, if I switch to the class Blowfish adapted, how would be the behavior with the rest of the passwords of the clients already registered? Would they be regenerated with the new encryption class? Would there be an incorrect password error for all clients already in the database?

Hello Fellows, I updated my php version to 8 using my store that runs php 1.7.8. After i updated it i got the following message that block me to get into mybackend, even if i use debug mode. (1/1) FatalErrorException Compile Error: Declaration of Doctrine\DBAL\Driver\PDOConnection::query() must be compatible with PDO::query(string $query, ?int $fetchMode = null, mixed ...$fetchModeArgs): PDOStatement|false in PDOConnection.php line 70 Any idea on how to solve it and fix it? Warm hugs Fabrizio

Acabo de actualizar PrestaShop de la versión 1.6.1.24 a la versión 1.7.8.6. Lo hice de la siguiente manera: Guarde todos los archivos en una carpeta llamada old, luego añadí los archivos del PrestaShop actual y luego subí las carpetas de img, themes, translation y modules. Una vez actualizado, al entrar al backoffice, no me aparece nada.(adjunto imagen) Donde puede estar el error? Gracias

Hola, Acabo de actualizar PrestaShop de la versión 1.6 a la 1.7. En el momento de entrar al backoffice, me aparece "Acceso denegado." Como puedo soliucionarlo? Gracias

Hi PrestaShop Lovers I attempt today to update manual as always the shop that i am working on When i tried to upgrade the DB with this command (install/upgrade/upgrade.php) as always do I got this error see image the site is working fine but after the update some deactivated modules and uninstalled came back so i had to remove it again Any thoughts?

Hi, sorry for my english I'm developping a module who needs to use my custom cart-detailed.tpl when the cart is updated. I overrided the function displayAjaxRefresh in CartController to use the tpl in my module. But I can't use my cart-detailed.tpl file. I tested the full path, path starting with 'module/',... After a great number of test i tried to do the same thing with the original cart-detailed.tpl but only the path 'checkout/_partials/cart-detailed' worked. Is it possible to use my template file in this controller ? And with which path ? Thanks, Alpha4

He creado de nuevo este tema, porque no he me han funcionado las soluciones de los otros. El problema es: No se vean las imágenes de los productos. He mudado un tienda de WP a Prestashop y luego he actualizado Prestashop a 1.7.8.2 para instalar los módulos SEO avanzado para PrestaShop y SEO friendly. Ahora no se ve ningún producto a pesar que se cargan (ver imane lo muestro con una flecha), muestra unos errores(la otra flecha). No consigo solucionarlo, he regenerado el .htaccess y las miniaturas, borrado y cargado de nuevo las images, he reemplazado los ficheros img/c y otros con los de la copia de seguridad, cambiado los permisos de las carpetas, etc... Puedo decir que todas las soluciones que he encontrado en los foros en español e ingles y en las búsquedas de internet.... Y se me han agotado las ideas y las soluciones encontradas... Agradesco una orientación de que hacer, gracias

Buenos días a todos, les comento acerca de mi problema: Mi web es: movileuropa.com Dicho problema va sobre el carrito de mi tienda online, cuando agregas un producto se añade correctamente al carrito(se abre el modal para ver que es lo que has agregado y que es lo que se desea hacer a continuación), pues cuando entras al carrito aparecen los productos añadidos todo de manera correcta y sin fallos. Hasta ahí todo bien, el problema viene cuando decido aumentar la cantidad de3 los productos los cuales el precio no se actualiza, no cambia ni el resumen del carrito ni el producto en si; solo cambian cuando actualizo manualmente la página con "F5" o dándole a recargar. Muchos de vosotros estaréis pensando de que hay varias publicaciones en el foro sobre este tema y en efecto así es, pero he realizado todo lo que dicen en esas publicaciones y nada, me sigue dando el mismo problema. También he buscado información en diferentes foros y páginas pero nada, no consigo arreglar el fallo. He accedido al archivo de configuración del carrito y el código está escrito correctamente de tal manera que debería funcionar; he probado a desactivar módulos no nativos de Prestashop; he probado además a desactivar la caché, el carrito ajax y varias cosas más pero aún así sigue fallando. Después de varias semanas intentando solucionar algo he podido conseguir que me muestre el error en la consola del inspector de Google, y os muestro el siguiente error: Este error solo sale cada vez que se debería ejecutar la acción de "updateCart", de otra manera no aparece. Por lo que puedo llegar a entender es que no puede leer la función 'cart' o es que no está definida, pero no entiendo el porqué si el código está bien escrito y no se ha tocado nada. Seguramente me faltará algo o será una tontería que ahora mismo no consigo darme cuenta, me suele pasar jajaja. Espero haberme explicado correctamente y que me podáis entender bien. Si me he explicado mal o necesitáis saber algo acerca del código no dudéis en decírmelo para que os lo muestre. A ver si entre todos podemos llegar a una solución y ayudar tanto a mi como a varias personas que les salga el mismo problema. Muchas gracias y un cordial saludo Natalio

PS 1.6.1.13 lgcookieslaw v1.4.20 -> 2.0.0 Modul EU Cookie Law (lgcookieslaw). By updating the above module I get this error when BO->Module refreshes to list Modules: Can anyone tell me what the error tells me? I tried to delete the module first and reinstall it but it's the same error. I tried to contact the module developer with no gain. So if anyone here knows about this kind of error - maybe it's just a file to delete before installing or a line to change. Any help or finger pointing is appreciated. Thanks for your precious time - it is appreciated! Pia

Vous souhaitez utiliser votre boutique et des modules prestashop sans être contraint de faire les mises à jour de ces derniers ? Vous voulez éviter à tout prix les problèmes qui résultent de ces mise à jour ? ce module est fait pour vous !!! L'installation du module supprime immédiatement toutes les contraintes qui empêchent d'utiliser un module à cause d'une mise à jour : La configuration du module vous donne la liste des modules qui devraient être mis à jour : Une simple désactivation (ou désinstallation) du module permet de revenir à la normale C'est ici, et c'est gratuit : version 1.0.0 noupdateplease.zip Testé sur 1.6.0.5 et 1.6.1 Mises à jour : VERSION 1.1.0 : v1.1.0.noupdateplease.zip permet de ne pas afficher les modules non installé sur le serveur ainsi que les modules à acheter VERSION 1.2.0 : v.1.2.0.noupdateplease.zip - suppression du bug qui n'affichait pas un module non encore installé ou désinstallé - ajout de 2 options dans la configuration du module ("Ne pas afficher les modules nécessitant une mise à jour" et "Ne pas afficher les modules absent du serveur") - ajout des logos des modules dans le tableau récapitulatif des modules à mettre à jour - ajout d'un tableau listant les modules non présent sur le serveur et normalement présent dans la liste des modules VERSION 1.3.0 : v.1.3.0.noupdateplease.zip - possibilité de sélectionner les modules dont on veut voir les mises à jour (modules de paiement par exemple) VERSION 1.4.0 : v.1.4.0.noupdateplease.zip - possibilité de désactiver l'addon onboarding et le configurateur de thème caché sur le front office Dernière version du module : https://www.coeos.pro/fr/modules-prestashop/115-pas-de-mise-a-jour-de-module-merci.html

Buongiorno, siccome sto avendo problemi ad aggiornare prestashop all'ultima patch tramite il modulo 1-Click (a causa di un timeout che mi da durante il backup dei file che lo stesso modulo genera) volevo sapere come posso aggiornare manualmente ps. C'è un file .zip da estrarre e copiare via FTP o simile? Grazie

One Click Upgrade + Update or Migrate PrestaShop to 1.7 Pro We present you the update PrestaShop module in 1 click: Upgrade your old version shop to the latest version of PrestaShop in one click with One Click Update or Migrate to 1.7 Pro. It's the best module to transfer your products, categories, and orders, all languages and all currencies and much more. Our tool saves an incredible amount of time and exports all types of data. The One Click Update or Migrate to 1.7 Pro module won the nomination favorite module PrestaShop and is a bestseller on PrestaShop Addons. The data transfer method is uniquely designed and checks all data for integrity before export. You can import this data and save many times: NEW Multistore export/import Easy to use Languages Image types Categories Attribute group Attributes Features Manufacturers Products Customer passwords (users can login with same data access)login with Product accessories Specific prices Specific price rules Customers Currencies Deliveries Carriers Carts Cart rules Orders Order invoices Orders details One Click PrestaShop Upgrade 1.6 to 1.7 transfer data from the old store to the new one, that is, it works only with 2 stores, then the old store can be deleted or 2 stores can be left. It is important that the module only transfers data, it will not be able to update your template or modules, there are no such modules, and you can order the adaptation of the template and modules separately from us. One Click PrestaShop Upgrade 1.6 to 1.7 is perfect for migrating your store from PrestaShop version 1.6 to version 1.7 In addition, you can try to update the store from version PrestaShop 1.4 to 1.5 or 1.6 and then import the products to 1.7 We are PrestaShop member since 2009 and seller since 2011:

Hi, I'm developing a module to call an API on update/create product. My scenario is that when this API is called, if successful, proceed with product create/update in prestashop. However, if the API for whatever reason fails, the product create/update must be prevented. Is there any way to do this in hookActionProductUpdate? Or is there another hook that I could use?

Buenos días, Estoy intentando actualizar mi tienda (actualmente dos prestashop diferentes teniendo el mismo problema) y tanto si lo hago con 1-click como si hago una actualizacion manual tengo problemas. Bueno con 1-click es como imposible hacerlo (nunca he conseguido k me lo haga bien pero esta vez casi peor que nunca) y manualmente me va todo bien salvo la ficha de producto en el admin (y en una de las dos tiendas ni sikiera el boton de añadir al carrito) por ejemplo, cuando abro la ficha de producto en el BO no funcionan los botones (ver producto, guardar, duplicar, volver al catalogo..) ni me carga las imagenes del producto (que se ven bien si abres el producto desde la tienda), he probado a usar el mismo AdminProductController.php de la version anterior y me carga tanto las imagenes como funcionan los botones (claro que la ficha es un caos por que esta todo descuadrado y algunas funcionalidades nuevas no van o se ven directamente un codigo ahi suelto) He probado a subir la version de php a 7.4 ya que esta verion 1.7.8 soporta php7.4 pero tampoco ha funcionado, si miro en la consola veo que hay un montón de errores js He probado varios navegadores y en todos pasa lo mismo... la verdad que estoy un poco perdida, no se si alguien ha tenido el mismo problema o sabe por que puede ser. Gracias de antemano, Un saludo

Hello there, After upgrading from 1.7.7.0 (or so) to 1.7.8.0 all of the icons on the front-end are gone. No more shopping-cart, no more login-in, no more menu button for mobile and so on. Also the arrows on the slider are missing. Tried to google for a solution but couldn't find anything usefull. I'm using the standard theme and I uploaded a picture for reference. Anyone a clue?

Nachdem Update von 1.7.6.5 auf 1.7.7.0 habe ich lediglich Zugriff auf die Übersichts-Seite im Back Office. Auf sämtlichen Seiten wird mir angezeigt: Wenn ich den Debug Modus aktiviere erhalte ich über Symfony Exception folgende Meldung: Attempted to call an undefined method named "setFallbackParameters" of class "Tools". Symfony\Component\Debug\Exception\UndefinedMethodException in src/PrestaShopBundle/EventListener/LegacyParametersListener.php (line 72) $legacyParameters = $this->converter->getParameters($request->attributes->all(), $request->query->all()); if (null === $legacyParameters) { return; } Tools::setFallbackParameters($legacyParameters); } } Im Frontend wird mir ein HTTP Error 503 angezeigt. UndefinedMethodException PHP Version 7.3 (mit 7.4. derselbe Fehler) MySQL Version 5.7 1-click Upgrade Version 4.11.0 Cache vorab gelöscht Hat jemand eine Idee, wo ich bei der Fehlersuche ansetzen könnte? Wäre über jede Hilfe dankbar. Gruß, Chris

Is it really necessary to download the entire product from api to update the price? I can send back such xml: <prestashop xmlns:xlink="http://www.w3.org/1999/xlink"> <product> <id><![CDATA[]]></id> <price><![CDATA[]]></price> <wholesale_price><![CDATA[]]></wholesale_price> </product> </prestashop> Unfortunately, not completed fields clear entries in the database. Is it possible to add a flag to the xml parsing function so that it does not update the absent fields? Thanks in advance for your help

When I updated the Prestashop version from 1.7.5.1 to 1.7.7.5, my HomeSlider is not showing. I checked the files between the two versions and they are the same. I am using AN Theme. PrestaShop version: 1.7.7.5 PHP version: 7.1.33

Ciao a tutti, Sto aggiornando in sandbox una copia del mio sito web prestashop live in MAMP (gratuito) seguendo questa iterazione: - il mio sito web è su 1.6.1.3 - Eseguo un aggiornamento da 1.6.1.3 a 1.6.1.24 con modulo aggiornamento in 1 clic e tutto va liscio, quindi cambio in MAMP il php da 5.6.40 a 7.1.33 e proseguo la disinstallazione e l'eliminazione (in questo ordine) di tutti i moduli e temi non nativi eccetto revws e payplug - Installo, in una diversa directory di htdocs e in un diverso database, un prestashop 1.6.1.24 e copio manualmente al suo interno i moduli revws e payplug, la cartella img e il file di impostazione - Cancello la directory 1.6.1.3 aggiornata a 1.6.1.24 e il database della nuova appena effettuata installazione 1.6.1.24 e collego, per mezzo di una copia del file settings, la directory prestashop 1.6.1.24 di questa nuova installazione al database dell'installazione 1.6.1.3 aggiornato a 1.6.1.24 e modifico la directory della nuova installazione 1.6.1.24 affinché combaci con quella originariamente aggiornata e che ora è stata cancellata - Quindi mi ritrovo con una nuova installazione di prestashop collegata al mio precedente database storico completo - In tutto questo processo ho mantenuto i moduli non nativi e gli override disattivati e ho eseguito il check up dei database con il modulo prestashop cleaner 1.8 e, una volta tornato al tema ufficiale, mi sono ritrovato ad una situazione molto "vanilla" e priva di errori se visulaizzata con la debug mode attiva. A questo punto, ho testato tutte le funzioni di questo sito web locale che mi ritrovo ibridato (vecchio database, nuova installazione) e tutto sembra andare bene, con nessun errore durante l'utilizzo della modalità di debug. Mi sento quindi a mio agio nell'usare il modulo 1-click per aggiornare a PS 1.7.7.4. - Metto lo zip nella cartella dei download e procedo con l'aggiornamento. Tutto fila liscio nell'aggiornamento dei file (tutto verde), ma quando il processo va al database, mi ritrovo con un errore e un back office poco accessibile, con front-office e back office zona ordini, clienti e setting inaccessibili a causa di troppi reindirizzamenti. Ecco la situazione e gli errori di aggiornamento del database: Updating database schema... Executing: CREATE TABLE ps_translation (id_translation INT AUTO_INCREMENT NOT NULL, id_lang INT NOT NULL, `key` TEXT NOT NULL COLLATE utf8_bin, translation TEXT NOT NULL, domain VARCHAR(80) NOT NULL, theme VARCHAR(32) DEFAULT NULL, INDEX IDX_ADEBEB36BA299860 (id_lang), INDEX `key` (domain), PRIMARY KEY(id_translation)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_module_history (id INT AUTO_INCREMENT NOT NULL, id_employee INT NOT NULL, id_module INT NOT NULL, date_add DATETIME NOT NULL, date_upd DATETIME NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_admin_filter (id INT AUTO_INCREMENT NOT NULL, employee INT NOT NULL, shop INT NOT NULL, controller VARCHAR(60) NOT NULL, action VARCHAR(100) NOT NULL, filter LONGTEXT NOT NULL, filter_id VARCHAR(191) NOT NULL, UNIQUE INDEX admin_filter_search_id_idx (employee, shop, controller, action, filter_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: DROP INDEX lang_iso_code ON ps_lang Executing: ALTER TABLE ps_lang CHANGE active active TINYINT(1) NOT NULL DEFAULT '0' , CHANGE iso_code iso_code VARCHAR(2) NOT NULL, CHANGE language_code language_code VARCHAR(5) NOT NULL, CHANGE date_format_lite date_format_lite VARCHAR(32) NOT NULL DEFAULT 'Y-m-d' , CHANGE date_format_full date_format_full VARCHAR(32) NOT NULL DEFAULT 'Y-m-d H:i:s' , CHANGE is_rtl is_rtl TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_2F43BFC7BA299860 ON ps_lang_shop (id_lang) Executing: ALTER TABLE ps_lang_shop RENAME INDEX id_shop TO IDX_2F43BFC7274A50A0 Executing: DROP INDEX id_lang ON ps_attribute_lang Executing: CREATE INDEX IDX_3ABE46A77A4F53DC ON ps_attribute_lang (id_attribute) Executing: CREATE INDEX IDX_3ABE46A7BA299860 ON ps_attribute_lang (id_lang) Executing: DROP INDEX deleted ON ps_shop_group Executing: ALTER TABLE ps_shop_group CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: DROP INDEX id_parent ON ps_tab Executing: DROP INDEX class_name ON ps_tab Executing: ALTER TABLE ps_tab ADD route_name VARCHAR(256) DEFAULT NULL, CHANGE position position INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE hide_host_mode hide_host_mode TINYINT(1) NOT NULL DEFAULT '0' , CHANGE icon icon VARCHAR(32) DEFAULT '' Executing: DROP INDEX id_shop_group ON ps_shop Executing: DROP INDEX id_category ON ps_shop Executing: ALTER TABLE ps_shop CHANGE id_category id_category INT NOT NULL DEFAULT '1' , CHANGE theme_name theme_name VARCHAR(255) NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_CBDFBB9EF5C9E40 ON ps_shop (id_shop_group) Executing: ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' 01:24:42 ERROR [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ':\n \n SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 """] In AbstractMySQLDriver.php line 106: An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE colo r color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 90: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 88: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 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]] [--] Avete qualche soluzione da suggerire? Come posso stabilire quali tabelle stanno provocando il problema per correggerle prima di procedere con l'aggiornamento 1.7.7.4? Grazie mille per qualsiasi suggerimento possiate fornirmi. Di seguito sono riportate le specifiche di MAMP al momento dell'errore: PHP: 7.1.33 max_execution_time30000 max_file_uploads20 max_input_nesting_level64 max_input_time60000 max_input_vars10000 memory_limit1024M post_max_size256M Server web: Apache [RISOLTO] Dopo aver postato il problema anche su stackoverflow mi è stato fatto notate che chiaramente il messaggio d'errore rimandava ad un campo regolato in database da un VARCHAR di massimo 32 caratteri spazi inclusi che si presentava popolato in eccesso. Trovato il campo, ridotto il contenuto da 35 a 29 caratteri e questo errore si è risolto, permettendomi di raggiungere il compimento dell'aggiornamento. In ogni caso, data l'eccedenza di errori da precedente installazione (database e prestashop vengono portati avanti, senza reset, dal 2013), ho collegato il database aggiornato alla 1.7 ad una fresh install 1.7. Attualmente ho dei problemi di permessi su tale nuovo database, ma questo problema è stato risolto.

Hi everyone, I am sandbox upgrading a copy of my live prestashop website in MAMP (free) following the iteration: - my website is a 1.6.1.3 - I perform an update of the stated 1.6.1.3 to a 1.6.1.24 with 1-click update and everything goes smooth, than I change MAMP from php 5.6.40 to 7.1.33 while uninstalling and deleting (in this order) all non native modules and themes except revws and payplug - I fresh install, in a different htdocs directory and in a different database, a 1.6.1.24 and I copy inside modules revws and payplug, the img folder and the setting file - I delete the 1.6.1.3 updated to 1.6.1.24 directory and the fresh install 1.6.1.24 database and connect the 1.6.1.24 fresh install to the 1.6.1.3 updated to 1.6.1.24 database and I modify the fresh install 1.6.1.24 directory to match the updated one that has been deleted - So I have a fresh install of prestashop connected to my previous historical complete database - In all of this process I kept non native module and overrides deactivated and performed multiple database checkout with module prestashop cleaner 1.8 and reverted to official theme, so a very "vanilla" situation. At this point, I tested all the functions of local website I find myself with and everything seems to go fine, no errors while using debug mode, so I feel comfortable in using 1-click module to update to PS 1.7.7.4. - I put the zip in the download folder and proceed with the update. Everything goes smooth in the files update (all green), but when the process goes to the database, I find myself with an error and a barely accessible back office, with front-office, and back office orders, customers and setting unaccessible due to too many redirects. Here you are the database update situation and errors: Updating database schema... Executing: CREATE TABLE ps_translation (id_translation INT AUTO_INCREMENT NOT NULL, id_lang INT NOT NULL, `key` TEXT NOT NULL COLLATE utf8_bin, translation TEXT NOT NULL, domain VARCHAR(80) NOT NULL, theme VARCHAR(32) DEFAULT NULL, INDEX IDX_ADEBEB36BA299860 (id_lang), INDEX `key` (domain), PRIMARY KEY(id_translation)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_module_history (id INT AUTO_INCREMENT NOT NULL, id_employee INT NOT NULL, id_module INT NOT NULL, date_add DATETIME NOT NULL, date_upd DATETIME NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_admin_filter (id INT AUTO_INCREMENT NOT NULL, employee INT NOT NULL, shop INT NOT NULL, controller VARCHAR(60) NOT NULL, action VARCHAR(100) NOT NULL, filter LONGTEXT NOT NULL, filter_id VARCHAR(191) NOT NULL, UNIQUE INDEX admin_filter_search_id_idx (employee, shop, controller, action, filter_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: DROP INDEX lang_iso_code ON ps_lang Executing: ALTER TABLE ps_lang CHANGE active active TINYINT(1) NOT NULL DEFAULT '0' , CHANGE iso_code iso_code VARCHAR(2) NOT NULL, CHANGE language_code language_code VARCHAR(5) NOT NULL, CHANGE date_format_lite date_format_lite VARCHAR(32) NOT NULL DEFAULT 'Y-m-d' , CHANGE date_format_full date_format_full VARCHAR(32) NOT NULL DEFAULT 'Y-m-d H:i:s' , CHANGE is_rtl is_rtl TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_2F43BFC7BA299860 ON ps_lang_shop (id_lang) Executing: ALTER TABLE ps_lang_shop RENAME INDEX id_shop TO IDX_2F43BFC7274A50A0 Executing: DROP INDEX id_lang ON ps_attribute_lang Executing: CREATE INDEX IDX_3ABE46A77A4F53DC ON ps_attribute_lang (id_attribute) Executing: CREATE INDEX IDX_3ABE46A7BA299860 ON ps_attribute_lang (id_lang) Executing: DROP INDEX deleted ON ps_shop_group Executing: ALTER TABLE ps_shop_group CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: DROP INDEX id_parent ON ps_tab Executing: DROP INDEX class_name ON ps_tab Executing: ALTER TABLE ps_tab ADD route_name VARCHAR(256) DEFAULT NULL, CHANGE position position INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE hide_host_mode hide_host_mode TINYINT(1) NOT NULL DEFAULT '0' , CHANGE icon icon VARCHAR(32) DEFAULT '' Executing: DROP INDEX id_shop_group ON ps_shop Executing: DROP INDEX id_category ON ps_shop Executing: ALTER TABLE ps_shop CHANGE id_category id_category INT NOT NULL DEFAULT '1' , CHANGE theme_name theme_name VARCHAR(255) NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_CBDFBB9EF5C9E40 ON ps_shop (id_shop_group) Executing: ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' 01:24:42 ERROR [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ':\n \n SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 """] In AbstractMySQLDriver.php line 106: An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE colo r color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 90: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 88: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 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]] [--] Do you have any solution to suggest? How do I address which tables are provoking the issue in order to correct them before proceeding with the 1.7.7.4 update? Thanks a lot for any suggestion provided. The following are the specifications of MAMP at the time of the error: PHP: 7.1.33 max_execution_time30000 max_file_uploads20 max_input_nesting_level64 max_input_time60000 max_input_vars10000 memory_limit1024M post_max_size256M Web server: Apache [SOLVED] After posting the problem also on stackoverflow I was made to notice that the error message clearly referred to a field regulated in the database by a VARCHAR of up to 32 characters including spaces which appeared to be populated in excess. Found the field, reduced the content from 35 to 29 characters and this error was resolved, allowing me to reach completion of the update. In any case, given the excess of errors from previous installation (database and prestashop are carried out, without reset, since 2013), I connected the database updated to 1.7 to a fresh install 1.7. I currently have permissions problems on this new database, but this specific issue has been fixed.