Leaderboard

MigrationPro. One of the best.

my bad! I am sorry for providing incorrect answer above, let's try this here is where change needs to take place https://app.screencast.com/SyusJDfc03CtI update with: data-interval="0" clear cache

Hello, This is a bootstrap carousel, not a swiper one. You can edit the following file: themes/hummingbird/templates/catalog/_partials/product-cover-thumbnails.tpl and on line 11, replace data-bs-ride="carousel" with data-bs-ride="false" If you have Template compilation set to Recompile templates if the files have been updated or Force compilation, the changes should be visible on page refresh. Otherwise, you will need to clear the cache.

Create a child theme.

Module upgraded. v1.2.0 (download from first post) added FLOOD filter to contact form. improved settings caching, works faster. prevent to bot or customer sent flood like: MWZGkZbrmrGTzop pmpBFMqwZlNfKSuE XjHipAKMB bFJRKwMqvhTEpF zBMHxAKpDs VbAXbdaRHxBDDjCmotFbom Check module settings/config. Basic value of "Message flood level summary" forming from other flood settings. Settings are adjustable.

If in db is correct, clear cache / browser cache and check.

@jamshidpour I solved it this way, follow these steps: 1. uninstall the edition_basic module 2. via ftp go to the modules folder and check that the ps_edition_basic folder is not there, if there is, delete it 3. go to the root folder of your project and then to var/cache and delete the prod and dev folders 4. go to your db ps_tab and ps_tab_lang, generally the Control Panel item is id 1 (check on ps_tab_lang), in the ps_tab table for the AdminDashboard classname set id_parent and position to 0 this is the right way

#Prestashop LiveFilter v5 FREE para ofrece a su sitio web de comercio electrónico Prestashop una forma innovadora de filtrar productos. CARACTERÍSTICAS: Plug & Play - configuración automática basada en los productos y la configuración de su tienda Clasificación “natural” - las opciones de filtro se clasifican “naturalmente”, como si los humanos leyeran listas Filtrado instantáneo - los productos se filtran a la velocidad del rayo, lo que da la impresión de obtener resultados instantáneos *Funciones avanzadas adicionales están disponibles en la versión PRO, más información aquí (ingles) - [addon] #LiveFilter v5 PRO 👉DESCARGAS: LiveFilter_v5.3.1_free ▶️DEMO (versión PRO): demo.endpulse.com Vista previa de la versión PRO:

Σας ευχαριστώ για την απάντησή σας. Διορθώθηκε με την πρώτη οδηγία σας. (1. Δοκίμασε Configure > Shop Parameters > Search και κάνε Rebuild entire index. Μετά καθάρισε cache Parameters > Performance και Clear Cache.)

Ben vous demandez aux auteurs de migrationpro.

Solution was on DB: Module Routes was being called to soon. So only needed to erase that entry from Hook module tables. DELETE FROM mod625_hook_module WHERE id_module = ( SELECT id_module FROM mod625_module WHERE name = 'ps_checkout' ) AND id_hook = ( SELECT id_hook FROM mod625_hook WHERE name = 'moduleRoutes' ); AND DELETE FROM mod625_hook_alias WHERE alias = 'moduleRoutes';

PrestaShop 8.1.7] Errore token nel Back Office con Cloudflare attivo (logout automatico). Buongiorno a tutti, utilizzo PrestaShop 8.1.7 su hosting condiviso Aruba Linux. Il sito è ottimizzato con Cloudflare (CDN + Proxy attivo) per migliorare la velocità, e funziona perfettamente dal lato front office. Il problema è il seguente: quando accedo al Back Office e inizio a caricare o modificare prodotti, dopo qualche minuto ricevo un errore di token non valido e vengo disconnesso automaticamente. Ho già provato quanto segue: Disattivato la cache e il “backed” nel pannello Cloudflare. Aggiunto eccezioni tramite Page Rules per /admin* e /login*. Inserito in .htaccess le direttive per preservare l’IP reale con CF-Connecting-IP. Pulito cache e cookie di PrestaShop. Testato anche con proxy disattivato (grigio), ma il sito diventa molto più lento. Nonostante tutto, l’errore persiste e continuo a essere buttato fuori dal back office. Qualcuno ha risolto un problema simile su hosting condiviso con Cloudflare attivo? Potrebbe trattarsi di una gestione errata dell’IP del client o della sessione PHP? Ogni suggerimento o configurazione funzionante è ben accetto. Il problema si risolve se disattivo il proxy . Ma il sito rallenta molto.

I moved a new version of a shop from a working directory to the root to make it the active shop. And then things went wrong: - Suddenly there was a javascript error with as a result that the TinyMCE editor no longer worked. The search field on the modules page didn't work either. The javascript error is in main.bundle.js - On the modules page there appeared at the top of the page the warning: 10 of your modules are no longer covered by Business Care - At the top right of the backoffice the buttons were pushed right and became clustered. I tried to disable ps_mbo but that crashed my backoffice. The only way to get it running again was to declare the module active in the ps_module table. In its new state the business care warning and the presence in the left side menu had disappeared but the javascript error remained. Later I also added the module again to the ps_module_shop table to fix a Stripe error that falsely claimed that the ps_eventbus and ps_accounts modules were no longer active. Does anyone have an idea how to solve this situation? PS version 8.2.3. ps_mbo version 4.14.0. Update: a day later the problem suddenly disappeared

Das lief doch normalerweise über das Benachrichtigungs-Modul, hast du das einmal resettet und die Einstellungen überprüft?

Thank you guy. Donated for a pair of beers Sweet greets from Spain!

carmen, justo cuando he acabado de escribir, he visto esto en las condiciones del módulo STKVerifactu, al menos son sinceros: IMPORTANTE: Exención de responsabilidad. Este módulo se proporciona sin una declaración responsable al no ser un Sistema Informático de Facturación (SIF). STK Verifactu es un módulo que dota a prestashop la funcionalidad de envíar facturas y devoluciones a la AEAT, añade código QR en PDFs y valida los datos fiscales del cliente según los requisitos técnicos oficiales, pero no puede garantizar otra serie de cosas que dependen del propio Prestashop que hace las veces de SIF, es tu responsabilidad auditar su código y usarlo de acuerdo a la normativa vigente. Para más información, consulta el Artículo 13 del RD 1007/2023. En resumen , es legal el módulo? NO, la responsabilidad es la misma que si lo programaras tu mismo, 100% tuya

Hello devs and users, I was strugling with this really bad behavior of Prestashop search engine when ie: you were searching for "wooden chair" and You end up with result of products that contains "wooden" and "chair" as well. Which sucks ass. This was driving my crazy so I end up with this override for Search.php in Prestashop 1.6 - didn't tested this on 1.7. This piece of code checks whether product that You searched for contains both or more words in search index (like tags, featuers not only the name) that You actually searched. Now I can die peacefully because when somone was searching for ie: Black chair he don't ends up with bunch of black wardrobes, chairs, sofas etc but actually only black chairs. To get this working at least in a relevant way please use at least (product name, features, categories, tags) or combinations set in Preferences -> Search. After this rebuild Your cache. Try not to use description or short description because it contains to many words. To install this just put this file in override/classes/ and after this remove class_index.php file in cache folder. I hope You find it usefull. I was working on this for 6 hours because I had to understand how prestashop search engine works (by the way - why the f*** presta needs to get all products from shop before searching!?) and I had to do this as efficient and performative as I can so any tip will be appreciated. It works faster for me then previous one. Try it for yourself If someone will find a better way to do this after reading this code please share it as well. I need to edit the file because previous contained a lot of my own overrides to search categories, cms and other stuff as well - now it's a clean one Update: I found much more efficient and easier method to get this done Edited again. Search.php

The first patch version for PrestaShop 9 is now available! This maintenance release focuses on resolving some of the key issues to ensure a smoother experience for all users.View the full article

i solved the problem to get 8.1.5 run back without the error again. but wait now for new version 9.0.1 till i try again upgrade. - i started to put the fresh prestashop 8.1.5 in a new folder. and backup the old folder safely. https://github.com/PrestaShop/PrestaShop/releases/download/8.1.5/prestashop_8.1.5.zip - delete the install folder. - copy my old database connection file /httpdocs/app/config/parameters.php into the new folder. - copy my old .htaccess into the new root folder. - copy my old custom "img" folder for productimages into the new folder. - copy my old custom "mails" folder for mailtemplates into the new folder. - copy my custom "modules" into the new folder. to figure out i compare the prestashop original modules with my old installed modules. - copy my custom "themes" (classic) into the new folder. - copy my custom "override" into the new folder. after all the site works in debugmodus without error and all old data, permalinks, images, mails, modules, themes & override work again!

Hi! Apologies for the delay. The new version contains many bugfixes and improvements therefore additional tests and devwork were needed. The release is delayed and rescheduled for mid-October. Regards, Daria 202-ecommerce

I am afraid that this is a limit from the VIES database itself. This is a problem outside of the VatChecker module. And it's actually the same problem you asked me before in July (here)

hola, nostros ya lo tenemos activo y funcionando, lo del estado que comentas, esta puesto como enviado, entregado,completo, en modo automático. como indicaron pondran para poder eleguir que estado para que sea creado automáticamente. si actualizaciones es 1 año como si fuera de prestashop addons, al menos eso dijeron, y se que vinculara con addons prestashop en el modulo de la web y asi para futuras actualizaciones saldra en la web.

Have you tried this instead: <i class="fa-brands fa-whatsapp"></i> <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.0/css/all.min.css">

Wgraj rozpakowane pliki modułu do folderu /modules/ potem odszukaj moduł na liście modułów i zainstaluj - ot proste obejście problemu.

Have you talk with Presta support team? try on https://care-center.prestashop.com/gb/contact-us?form=sales either PS account module page support: https://addons.prestashop.com/en/website-security-access/49648-prestashop-account.html

This is embarrassing. The person adding images didn't choose the extra images in the Combinations tab. Groan. I fixed it in 2 minutes after spending hours looking around for server-related problems. I'll mark this Solved. Sorry for my error!

Hi all, I know this version is quite old now, but sharing a fix I had to implement on a PrestaShop 1.7.6.7 site with multi-currency enabled. Posting here because I couldn’t find a clear solution for this specific case anywhere. The issue: When an order was placed in a non-default currency (e.g. shop base in EUR, customer pays in CHF), the order itself showed the correct totals in the order currency. But in ps_order_detail, the product line prices (product_price, original_product_price, unit/totals) were stored in the shop’s base currency. This meant inconsistencies: order summary looked fine, but the order details showed the wrong currency values (in BO and order confirmation emails). To resolve, you need to override OrderDetail class. Drop this into /override/classes/order/OrderDetail.php and clear cache: <?php class OrderDetail extends OrderDetailCore { /** * Set detailed product price to the order detail. * * @param Order $order * @param Cart $cart * @param array $product */ protected function setDetailProductPrice(Order $order, Cart $cart, $product) { $currency = new Currency((int) $order->id_currency); $this->setContext((int) $product['id_shop']); $id_tax_address = (int) $order->{Configuration::get('PS_TAX_ADDRESS_TYPE')}; $nullVar = null; $price_tax_incl = Product::getPriceStatic( (int) $product['id_product'], true, (int) $product['id_product_attribute'], 6, null, false, true, $product['cart_quantity'], false, (int) $order->id_customer, (int) $order->id_cart, $id_tax_address, $nullVar, true, true, $this->context ); $price_tax_excl = Product::getPriceStatic( (int) $product['id_product'], false, (int) $product['id_product_attribute'], 6, null, false, true, $product['cart_quantity'], false, (int) $order->id_customer, (int) $order->id_cart, $id_tax_address, $nullVar, true, true, $this->context ); $price_tax_incl = Tools::ps_round($price_tax_incl, 6); $price_tax_excl = Tools::ps_round($price_tax_excl, 6); $converted_excl = Tools::convertPrice($price_tax_excl, $currency); if ($converted_excl === false || $converted_excl === null) { $converted_excl = 0.0; } $this->original_product_price = (float) Tools::ps_round($converted_excl, 6); $this->product_price = $this->original_product_price; $this->unit_price_tax_excl = (float) Tools::ps_round(Tools::convertPrice((float) $product['price'], $currency), 6); $this->unit_price_tax_incl = (float) Tools::ps_round(Tools::convertPrice((float) $product['price_wt'], $currency), 6); $this->total_price_tax_excl = (float) Tools::ps_round(Tools::convertPrice((float) $product['total'], $currency), 6); $this->total_price_tax_incl = (float) Tools::ps_round(Tools::convertPrice((float) $product['total_wt'], $currency), 6); $this->purchase_supplier_price = (float) $product['wholesale_price']; if ($product['id_supplier'] > 0 && ($supplier_price = ProductSupplier::getProductPrice( (int) $product['id_supplier'], $product['id_product'], $product['id_product_attribute'], true )) > 0 ) { $this->purchase_supplier_price = (float) $supplier_price; } $this->setSpecificPrice($order, $product); $this->group_reduction = (float) Group::getReduction((int) $order->id_customer); $shop_id = $this->context->shop->id; $quantity_discount = SpecificPrice::getQuantityDiscount( (int) $product['id_product'], $shop_id, (int) $cart->id_currency, (int) $this->vat_address->id_country, (int) $this->customer->id_default_group, (int) $product['cart_quantity'], false, null, null, $nullVar, true, true, $this->context ); $unit_price = Product::getPriceStatic( (int) $product['id_product'], true, ($product['id_product_attribute'] ? (int) $product['id_product_attribute'] : null), 2, null, false, true, 1, false, (int) $order->id_customer, null, $id_tax_address, $nullVar, true, true, $this->context ); $unit_price = Tools::ps_round($unit_price, 6); $this->product_quantity_discount = 0.00; if ($quantity_discount) { $this->product_quantity_discount = $unit_price; if (Product::getTaxCalculationMethod((int) $order->id_customer) == PS_TAX_EXC) { $this->product_quantity_discount = Tools::ps_round($unit_price, 6); } if (isset($this->tax_calculator)) { $this->product_quantity_discount -= $this->tax_calculator->addTaxes($quantity_discount['price']); $this->product_quantity_discount = Tools::ps_round($this->product_quantity_discount, 6); } } $this->discount_quantity_applied = ( ($this->specificPrice && $this->specificPrice['from_quantity'] > 1) ? 1 : 0 ); } } ✌️

Pour l'année 2025, seul le mois de janvier avait plus de commandes que le mois de janvier 2024 (+4%) tous les autres mois par rapport aux mois de l'année 2024 sont en baisses. Du 1er janvier au 30 septembre 2025 le nombre de commande est à -7% par rapport à la même période 2024. Shopify continue sa bonne progression là ou PrestaShop continue lentement mais sûrement sa dégringolade : https://trends.google.fr/trends/explore?date=all&geo=FR&q=prestashop,shopify&hl=fr

You have active more then one language so you must provide products names in all languages.

Same issue here after updating ps_account module

Bonjour, non vous n'etes pas chiant et merci de vous impliquer. ET oui c'est bien celui la que j'ai acheté, le moins cher https://addons.prestashop.com/en/data-transfer-backup/50731-migrationpro-advanced-easy-migration-upgrade-tool.html Comme je disais c'est par le panneau client que j'ai eu accès au support que je ne trouvais pas. Bilan de ce logiciel : Génial et le support client est exceptionnel d'efficacité et de réactivité. tous mes problemes ont été résolus, la migration s'est faite parfaitement, avec des produits à de multiples declinaisons, toutes les pages ont migré correctement, meme les pages CRM. Je suis en phase de bascule /remplacement du nouveau vers l'ancien et enfin je vais arreter de payer du support PHP ... A suivre

Thank you very much

In V3 what was the threshold used?

I didn't realize that the themes offered by Presta Shop were so flawed. The standard theme was unacceptable to me because it formatted the item view poorly when there was a lot of information. Apart from the checkout error, Hummingbird would work well enough for me. I took a look at the CSS developer—it seems to be quite powerful. So now I'm looking for someone to remove the bug in the CSS file. Just send an email to [email protected] Thank you very much.

If I can suggest an improvement, if there's not already a module's log file you could consider to implement it... this could be useful to find what's gone wrong in events like my previous one

Well, the French market to the French, loool. I’m the same—I market in English. In Chrome you can just right-click (if your mouse has a right-click button) and choose “Translate” to view any page in your language. Yes, translators can be expensive, and for some shops that cost is prohibitive. But there are plenty of PrestaShops generating enough sales that they can budget for professional translations. Here’s a link to some translation modules (though they do look a bit pricey): https://addons.prestashop.com/en/search?search_query=translation+module Another option is simply using AI for translations. For example, you could export the required data with SQL, run it through AI to translate, then reupload it. First, you’d need to add the translation pack. I’d recommend testing this on a staging copy first—but it seems very doable. translated to spanish via chatgpt Bueno, el mercado francés para los franceses, loool. Yo igual: hago marketing en inglés. En Chrome puedes hacer clic derecho (si tu ratón tiene botón derecho) y elegir “Traducir” para ver cualquier página en tu idioma. Sí, los traductores pueden ser caros, y para algunas tiendas ese costo es prohibitivo. Pero hay muchas PrestaShops que generan suficientes ventas como para presupuestar traducciones profesionales. Aquí tienes un enlace a algunos módulos de traducción (aunque se ven un poco caros): https://addons.prestashop.com/en/search?search_query=translation+module Otra opción es simplemente usar IA para las traducciones. Por ejemplo, podrías exportar los datos necesarios con SQL, pasarlos por IA para traducirlos y luego volver a subirlos. Primero tendrías que añadir el paquete de traducción. Recomiendo probarlo en una copia de pruebas (staging) primero, pero parece muy factible.

Cheval de Troie piraté. Activez le mode maintenance pour plus de sécurité. Analysez la boutique https://www.prestashop.com/forums/topic/1067200-hack-prestashop-sur-la-page-de-paiement-nettoyage/ et envisagez une mise à jour. La version 1.6 n'est pas sécurisée.

Bonjour, J'ai un problème similaire. Je tente la mise à jour des modules, dans le BO, on m'indique que c'est fait, mais les modules restent en "Mettre à jour". J'ai vidé le cache, et suivi les infos au dessus mais ça n'a pas fonctionné. Mais j'ai trouvé une solution simple. Mettre à jour le module le desactivé le désinstaller l'installer de nouveau C'est un peu long mais ça fonctionne Version de PrestaShop : 9.0.0 Thème actif : hummingbird Version de PHP : 8.2.28 Version de MySQL : 10.11.10-MariaDB

The problem solved. It was in root/classes/controller/FrontController.php:1709 1) 'favicon' => self::configuredImageUrl('PS_STORES_ICON', $psImageUrl), The mistake was here, just updated "PS_STORES_ICON" to correct key "PS_FAVICON". Then cleared cache.

Edit src/Core/Context/CurrencyContextBuilder.php around line 62, and cast integer fields to string explicitly. // Update to: $currencyContext = new CurrencyContext( (int) $currencyId, (string) $isoCode, (int) $precision, // ... ); Clear PrestaShop cache, then reload the backend. or install it manually by uploading the Zip file directly.

A customer contacted me with the same problem. Here is his latest response. if it can help you

En 1.7 :

Ben avant il y avait une option mais maintenant ils s'en tamponnent et le mettent forcément en l'injectant depuis le header. Il faut le cacher en css. /* Bad paypal advertising */ #ps_checkout-payment-method-logo-block-container { display:none; visibility:hidden; height:0; } #ps_checkout-displayPayment .ps_checkout-payment-option div.payment_module a { font-weight: 300; }

Gdyby co dostałem informacje i należy doinstalować moduł v6.3.2-ps-accounts.zip i wszystko zadziałało !

If your current version isnt latest 1.6 first upgrade to latest using official module: https://github.com/PrestaShop/autoupgrade From 1.6 to 1.7 use this module:or From 1.7 to 8.1 use official module: https://github.com/PrestaShop/autoupgrade This method allows to migrate all data even theme but its going not best solution if you want you website to works and looks good. Faster and better option is to use: With this you need to create fresh installation of prestashop and move data from old shop to new. This options is alot faster and final result its stable website with old data.

You need to navigate to your BO => Modules => Module Manager => search for the psgdpr module => configure it => Click on the third Tab" Consent checkbox customization" & edit the "Consent request message"

any solution?

J'ai trouvé la solution en espérant que cela aide d'autres personnes. Prestashop à mal géré le système dommage car il génère bêtement les Règles de Taxes. Prenons l'exemple d'un produit dont la règle de taxe est FR Taux standard (20%) dans l'onglet prix dans la fiche produit. Je vais dans les taxes et je regarde que toutes les taxes sont bien crées (Attention pour la suisse on est à 7,7% aujourd'hui le 8% était avant 2018) Une fois toutes les taxes ok, on va dans les règles de taxe. Vu que sur ma fiche produit j'ai utiliser la taxe FR 20% je vais modifier la ligne ou il y a le FR Taux standard (20%). Une fois dedans on a tous les pays que l'on a importé lors de l'ajout d'une langue mais toutes les taxes sont à 20% pour les pays. Grosse erreur de prestashop, il faut modifier le taux de tous les pays un part un et lui mettre le bon taux. Une fois cela fait vous pouvez faire des tests de commandes avec l'adresse de facturation différentes et vous verrez le taux changer. C'est très subtile comme détail mais après des jours de recherche j'ai enfin trouvé et j'espère que cela en aidera plus d'un.

Customers > Addresses > Set required fields for this section > Phone_mobile Make sure youre added in locations > countries > phone_mobile