Leaderboard

Le répertoire /classes était totalement corrompu. Le problème est désormais résolu.

Im Kontaktformularmodul unter modules\contactform\contactform.php finden sich die erlaubten Dateiendungen in der Funktion sendMessage. Wenn das upgradesicher erweitert werden soll, musst du ein Modul-Override erstellen (https://devdocs.prestashop-project.org/9/modules/concepts/overrides/#override-a-module) public function sendMessage() { $extension = ['.txt', '.rtf', '.doc', '.docx', '.pdf', '.zip', '.png', '.jpeg', '.gif', '.jpg', '.webp'];

https://prestaheroes.com/blogs/prestashop-alerts/prestashop-s-ownership-change-exposed-a-deeper-problem-why-shopify-ate-its-liver

La sortie de PrestaShop 9 a malheureusement été un désastre en termes de gestion de version. La version 9.0.0 a été présentée comme la version « actuelle » à télécharger, ce qui a donné aux nouveaux administrateurs — ainsi qu’aux marchands existants — l’impression qu’il était sûr d’installer ou de mettre à jour, alors que ce n’était clairement pas le cas. S’appuyer sur la communauté pour tester une version majeure sur des boutiques en production est un très mauvais modèle, et de nombreux marchands en ont subi les conséquences. Espérons qu’avec la nouvelle direction de PrestaShop, cette mauvaise pratique cessera et que les futures versions majeures ne seront plus mises en avant comme étant prêtes pour la production avant de l’être réellement. Ce n’est qu’avec la version bêta de PrestaShop 9.1 que PrestaShop a clairement indiqué qu’elle n’est pas destinée aux administrateurs “classiques” et non techniques, ni à une mise à jour de boutiques en production. Tant qu’une version 9.x réellement stable n’existe pas, PrestaShop 9 doit être évité en production, en particulier par les utilisateurs non techniques.

Hi, I have managed to change the currency successfully following these steps: 1. Add EUR as a new currency. 2. Set the correct conversion rate between BGN and EUR. PrestaShop will calculate prices automatically based on that rate. (optional, even if you don't do it when switch off BGN, the prices will remain the same w/out change ) 3. Set EUR as the default shop currency. 4.Disable BGN. You will see that after these steps, the prices will remain the same as they were, but in the new currency EUR. 5. Than you need to execute the following SQL queries: -- Convert base product prices from BGN to EUR UPDATE ps_product SET price = ROUND(price / 1.95583, 2), wholesale_price = ROUND(wholesale_price / 1.95583, 2); Convert shop-scoped prices (used even in single-shop installs) UPDATE ps_product_shop SET price = ROUND(price / 1.95583, 2), wholesale_price = ROUND(wholesale_price / 1.95583, 2); Now, everything should be ok. I realized that you need also to make two additional steps: 6. Change the prices of the transport! 7. Payment methods -> Settings: These were unchecked and I had to check them, because the currency was changed.

In PrestaShop 9, the order status email preview does not use your theme’s custom email templates. The preview pulls emails from the core fallback location, not from overridden theme folders. This is expected behavior and does not reflect what customers actually receive. Actual emails sent to customers will still use the correct theme and language templates. The preview tool is mainly for basic testing, not full template validation.

Hi, In PrestaShop 9 the “Order status” email preview isn’t driven only by the old /mails/en/*.html files anymore. It uses the Twig email theme system, so it’s normal that footer.twig changes show up (Twig layout), while the main body still looks generic if you’re editing the wrong layer. What to do: BO → Design > Email theme: select your email theme and click Generate. Edit the Twig templates in /mails/themes/classic/ (templates/layouts/components), not just the language folder. Clear cache. And yes, preview breaking when /mails/themes/classic is missing looks like a fallback/bug, keep that folder.

Hallo, Wenn Ihr Shop im Debug-Modus läuft, aber nicht im normalen Modul, müssen Sie in den meisten Fällen lediglich den Cache manuell leeren: https://www.mediacom87.fr/en/faq-how-to-clear-the-cache-manually-on-prestashop-17/

Hej, jak w temacie potrzebuję wprowadzić do swijego sklepu konfigurator który będzie wyświetlał warianty rozmiarowe po wybraniu modelu i rocznika samochodu. mam wstepnie przygotowany taki konfigurstor oparty gdzie kategorie i podkategorie sa mpodelami i rocznikami aut, natomiast lista pasujacych felg wyświetla się podczepiona jako link wygenerowany przez moduł Advanced search 5. ale 1 problem że konfigurowanie tego jest mozolne, a wczytywanie wyników trochę za powolne. może da sie to zorganizować lepiej i sprawniej.

I'm giving it away for free. If you post anything on the forum, it's the property of the forum. When I asked in the past to delete my account and all my uploaded files and modules, I was told that no content can be deleted! I don't need promotion. I've already sent the module to four interested parties yesterday. If you find a similar topic on the forum, I've already posted information on how to do it. If you think my post is defective, you can report it and send it to the administrators for review.

Ok, so heres's the deal with this. Apparently Prestashop moved from swiftmailer (with PS 8 ) to symfony mailer (with PS 9). It appears that my host was blocking the new mailer from sending the emails externally. We had to change our SMTP settings to a gmail server to get it to work. We're not sure what changed between mailers, but this should not be a thing and needs to be looked at within Prestashop. I've seen other people with the same issue.

Merci pour votre aide. Un de vos collegues ayant pris la main a résolu le probleme

@Thierry L Bonjour Thierry, Je suis d'accord avec vous j'aurai bien aimé que la carte (même si aucun prélevement n'est effectué en version gratuite) ne soit pas demandé, je comprend la contrainte et j'aurai aimé que cela soit différent mais c'est le module billing de Prestashop qui impose cela. Peut-être que Prestashop changera ce process dans le futur en attendant bonne continuation, Bonne journée

Hello everyone! 👋 I've been a PrestaShop developer for over 10 years and I've just released a module I've been working on for a while: MedBrain. --- 🧠 The problem it solves You probably know this situation: An employee changes the wrong product price A category gets deleted by mistake A CSV import overwrites descriptions you carefully wrote You spend hours trying to figure out "what it was like before" PrestaShop doesn't have a native object history and restore system. Once modified or deleted, it's (almost) irreversible. --- 💡 The solution: MedBrain MedBrain automatically records every creation, modification, and deletion made in your back-office and lets you restore any previous version with a single click. It's like a Ctrl+Z for your entire store. --- ✨ Main Features Automatic Tracking: Transparent recording via native PrestaShop hooks 1-Click Restore: Undo any modification instantly Detailed Comparison: View before/after differences for each field Full Traceability: Who did what, when, from which IP Fully Configurable: Choose which classes to track and which fields to ignore Automatic Cleanup: Set a retention period to manage disk space --- 📊 Tracked Objects The module can track over 50 PrestaShop classes, including: | Main Objects | Other Objects | |--------------|---------------| | Product | Attribute | | Category | Feature | | Customer | Carrier | | Order | Manufacturer | | Address | Supplier | | Employee | CMS | You select exactly what you want to track in the configuration. Presentation: https://ps8.mediacom87.net/medbrain/landing-en/

une pour les 2

Ok, I will ask my web space provider (ionos) to fix the problem. If they not can fix it I will need an good Prestashop Agency for installing.

Merci. Je vais faire ça

Bug résolu avec l'aide @Eolia .... merci beaucoup et de ChatGPT Etape 1 - Modification cateogry-header.tpl <div id="js-product-list-header"> {if $listing.pagination.items_shown_from == 1} <div class="block-category card card-block"> <h1 class="h1">{$category.name}</h1> {* Textes utilisés par le JS "Voir plus / Voir moins" (doivent exister dans le DOM) *} <span id="readmore" style="display:none;">Voir plus</span> <span id="readless" style="display:none;">Voir moins</span> <div class="block-category-inner"> {if $category.description} <div id="category-description" class="text-muted"> {$category.description nofilter} </div> {/if} {if !empty($category.image.large.url)} <div class="category-cover"> <img src="{$category.image.large.url}" alt="{if !empty($category.image.legend)}{$category.image.legend}{else}{$category.name}{/if}" loading="lazy" width="141" height="180"> </div> {/if} </div> </div> {/if} </div> Etape 2 - Modification du custom.css avec l'ajout de : /* Cache la version longue de la description par défaut */ .text-muted .more_text { display: none; } /* Cache le bouton "Voir moins" par défaut */ .text-muted .read_less { display: none; }

Prestashop works higher than 8.1 This is my install on 8.2.30

I hope it will help the platform to become more stable and predictable 🤞

J'ai fini par réussi à aller au bout de la mise à jour en ne gardant que les modules natifs , la page mise à jour réussie s'est affichée mais par la suite je n'avais plus accès au gestionnaire des modules (page blanche) et après avoir vérifier plusieurs onglets pour voir si le reste fonctionnait j'ai eu un bug , le tout s'est mis en erreur 500. l'hebergeur m'a dit que c'était du à un module qui provoquait trop de requêtes mais je ne sais pas lequel, en mode debug je n'avais rien. Retour à la 8 pour l'instant

N'effectuez pas la mise à jour vers la PS9 tant qu'elle n'est pas stable. Même si la mise à jour réussit, vous rencontrerez de nombreux problèmes. Beaucoup d'utilisateurs rencontrent des problèmes avec la PS9.

A few important clarifications that are often glossed over in the forum: PrestaShop 9.0.x was marketed as stable In reality, it behaved more like an extended release candidate. Core workflows (including International → Locations → States/Provinces) have produced regressions, validation errors, and UI inconsistencies that simply did not exist in mature 1.7 or 8.x branches. Current reality: 9.1 is still beta The currently announced 9.1.x line is explicitly a beta. By definition: It is not intended for common use It assumes advanced users, staging environments, and log-level debugging Merchants should expect breakage, schema changes, and unfinished features That alone should have been communicated much more clearly. Community “testing” ≠ informed consent Year after year, the same pattern repeats: A major version is labeled “ready” Merchants upgrade in good faith Real-world issues surface The community ends up discovering and reporting problems post-release I highly recommend and what should be stated by seasoned PrestaShop users is that PS9 is not ready, to not use ps9 but an earlier version or just find another ecommerce platform, there are plenty and none use the business module that PrestaShop uses. PrestaShop lost so much market share doing things like this, ps9 has NO must have feature, PrestaShop does this so people have to repurchase modules and themes, none of which are very good. If you want a stable PrestaShop then use 8.2.3. I challenge other forum members to speak the truth to new users and who got tricked in ps9, use any previous stable version. Hopefully the new owners of PrestaShop will put an end to this, I think they will.

Hi, Musicmaster, I got advice from my hosting on this issue. First of all they agree that this is cause by some upgrades to server (DD, SQL or php), but it can't be downgraded because of security and because it is shared server. So looking into login1.php code they advised to ignore warnings in that particular place of the code. Adding this around original code: $old_level = error_reporting(); error_reporting($old_level & ~E_WARNING); // original code block with mysqli_connect error_reporting($old_level); I added it and it actually it did the trick. At least Combination_delete now works as it used before. I am not sure if it is a good practice for you to add it tot the code as standard. If you see it not usable, I believe I'll need to update login1.php manually every time I take an update from your website. On your POV - can this cause any issues? Thanks!

Bonjour, Le problème venait du module "Customer Activities - Track/View customer behavior" de PrestaHero, je l'ai désinstallé. Merci pour votre aide, si cela peut servir. Cordialement

It was a 3rd part module (officially compatible with PS 9) giving troubles. Thank you all

Hi, New user here, I just installed Prestashop 8.2.0, I want to add simple javascript/jQuery code right before </body> ? What file should I edit? or should I do it via backend? Thank you.

Hallo Caroline, vielen Dank für deine Antwort. Aber das löst mein Problem nicht. Ich kann bei meiner Standardversandart überhaupt gar nichts auswählen. Ich würde da gerne DHL-Paket hinterlegen. Ich überlege, ob es an den voreingestellten Versandkosten liegt, die sind nämlich nur 3 Euro, was natürlich zu wenig für ein Paket ist. Ansonsten sind alle Versandeinstellungen identisch mit "Gerollte Poster plus andere Waren" - und da kann ich "DHL-Paket" einstellen. Ich verschicke diese Sendungen normalerweise als Briefpost, aber bei größeren Bestellungen, die die 1.000 Gramm Marke knacken, verschicke ich es als Paket und übernehme die Mehrkosten. Diese Bestellungen muss ich jetzt im DHL-Portal mühsam per Hand eingeben.

J'ai dû cliquer sans m'en apercevoir. Il était bien en mode démo. Pfff...!! 🙃 Pourtant j'ai pas trop abusé pendant les fêtes 🍷 Merci beaucoup

Le bouton Mode démo en haut à droite ne serait-il pas actif par hasard ?

Най-лесно е през CLI директно да промените цените, както е написал El Patron на 2 януари. Току що го направих и работи. Не забравяйте да направите backup преди промяната, за да можете да се върнете, ако има проблем.

TreRuote Have you managed to locate the causes of this problem? I have a similar one, and a lot of processes appeared. The first temporary solution that allowed me to restore the shop to working order, but did not definitively solve the problem, was to disable the Lightspeed Cash module. I simply changed its name via FTP, and even though the large number of processes did not disappear, the shop started to function somehow. (I hope this will help someone in the future.) However, I still do not know what causes the processes to get stuck in large numbers.

Dieses Problem tritt meist auf, wenn das gewählte DHL-Produkt nicht zum Versandtyp passt. Was du prüfen solltest: Stelle sicher, dass Warenpost nur für zulässige Länder, Gewichte und Maße verwendet wird. Prüfe, ob dein DHL-Geschäftskonto Warenpost für die betroffenen Regionen wirklich aktiviert hat. Testweise den Versanddienst auf DHL Paket (Standard) umstellen – wenn das funktioniert, liegt das Problem eindeutig an Warenpost. Falls verfügbar, Debug/Log-Funktion im DHL Modul aktivieren, um die API-Antwort zu prüfen. In den meisten Fällen behebt der Wechsel von Warenpost zu DHL Paket das Problem sofort.

Thanks for the explanation, much appreciated , but still a shame not to be able to make narrow searches here especially to find things that have probably already been answered and for which people who actually are keen on helping stop helping because they already have answered same topics numerous times, but is what it is

maybe this helps, also always post the exact prestashop version and php version. How to check if the Experimental Product Page is enabled In the Back Office, go to: Advanced Parameters → New & Experimental Features Look for: New Product Page (or similar wording) If it is enabled, you are using the experimental Symfony product editor How to disable it (recommended for stability) To revert to the stable, legacy product page: Go to: Advanced Parameters → New & Experimental Features Disable: New / Experimental Product Page Save Clear cache: o Back Office: Advanced Parameters → Performance → Clear cache o Or manually delete /var/cache/* on the server Log out and log back into the Back Office After this, product editing and duplication will use the legacy product controller, which is significantly more stable and does not suffer from the endless-clone issue.

If you view the page source, you’ll see that links on forum topics are marked as nofollow. This is a hint to search engines not to pass ranking value (and often not to index the linked content, although they sometimes still do). Because of this, it’s usually better to search outside the PrestaShop forum if you’re looking for broader or more complete results. AI tools can also be helpful, as they often surface relevant PrestaShop GitHub issues, which tend to contain much more useful technical detail. You can do the same with regular Google or other search engines by explicitly including terms like: PrestaShop GitHub issue or PrestaShop GitHub question.

Main region is in the UK

Hi — this may help, and @Daresh is also correct. now we discuss 101 times...loool Using phpMyAdmin, you can sort your database by table size and row count to quickly identify which tables are growing abnormally. Without doing this, you are essentially guessing and won’t know where the actual bloat is coming from. Be aware that some modules store caches and logs in database tables, and these can grow very large over time if not managed properly. How to find large tables using phpMyAdmin: Log in to phpMyAdmin from your hosting control panel. Select your PrestaShop database from the left sidebar. Click the Structure tab (this is the default view). Scroll to the bottom of the table list and ensure the following columns are visible: Rows Data length Index length Size Click the Size column header to sort tables by total size (Data + Index). Alternatively, click Rows to sort by row count and identify log- or cache-heavy tables. Tables that stand out as unusually large are typically the source of database growth and performance issues. Here is an article that outlines common PrestaShop tables that tend to grow large, and which ones can typically be safely emptied or pruned (depending on your setup): https://prestaheroes.com/blogs/mysql-optimization/which-large-prestashop-tables-can-be-dropped-or-emptied-safely

That is really useful advice, thank you El Patron! Any particular companies/packages you recommend? Currently get about 100 orders per day then about 250/day in peak season.

Bonnes fêtes à tous, profitez 2026 arrive... Les chiffres sont plus mauvais que jamais : moins de nouvelles ventes en 2025 qu'en 2011, même le nombre de BC à l'air en baisse ce qui prouve que ça n'intéresse pas les clients : Pour la première fois les recherches sur google sont plus importantes pour WooComerce que PrestaShop : https://trends.google.fr/trends/explore?date=all&geo=FR&q=prestashop,shopify,WooCommerce&hl=fr Même la team ne prend plus la peine de rédiger la Marketplace Guidelines, c'est chatGPT qui s'en charge : https://docs.cloud.prestashop.com/3-content-and-marketing-standards/ il y a encore quelqu'un à bord ?

You have fixed many on-page things already nice work. To move higher focus on authority: Get some quality backlinks Improve internal links to key products Add new helpful content regularly Google needs strong trust signals to push you to the top.

I got the same error. The weirdest part about this error is that it didn't show up in a local and an ubuntu vps installation but it does break on my managed hosting environment. There is a discussion here https://github.com/PrestaShop/PrestaShop/issues/38894 but the hosting environment is never mentioned. edit: The environment was mentioned here after all https://github.com/PrestaShop/PrestaShop/pull/38905 tl;dr make the following changes https://github.com/PrestaShop/PrestaShop/pull/38905/files and the backoffice will probably be fixed.

2.4.3 - 14/02/2025 Ajout d'un contrôle des fichiers modifiés par tâche Cron, avec alerte par courrier électronique Cette nouvelle fonctionnalité vous permet de recevoir une notification par e-mail en cas de modification des fichiers natifs de PrestaShop depuis la dernière analyse. Un outil idéal pour surveiller l’intégrité de votre boutique en toute simplicité.

TLDR: The server timezone could be different than the time applied to the start date for the voucher. Roll back the start time of a voucher to check. I figured it out, but I couldn't find any info on the issue, so here you go: This is what happened to me and how to fix it: I have a module that create account-specific codeless vouchers as referral rewards, these would apply automatically on checkout. Tried it all locally and no issue. When I installed said module on my live site, the email notifying of the voucher's creation was working, but the vouchers didn't display on My Vouchers in the customer's My account or apply on checkout. Reinstalled everything, still didn't work. Turns out, my server's timezone was UTC, but the vouchers were being created with the "from x date" setting being GMT+1 —one hour after—, so the vouchers wouldn't show up until an hour had passed from the voucher creation time —and patience is clearly not my thing. Try to roll back the time of a voucher's start date, see if that works. If it does, change the server's timezone.

Je viens à nouveau de remonter le problème depuis le site Thales, mais ils me demandent d'avoir un compte pour traiter la demande... Je réponds quand même on verra ....

Thanks for the tip, I wanted to try, but the developer's support has completely stopped and I can't even contact him through a ticket - because to create a ticket, you need to extend the support. And to be honest, I don't want to renew support for €70 because of this problem

Data is saved in ps_module_carrier. ID Module -> payment module id ID Reference -> carrier id reference (from ps_carrier table)

You can check out my "Please choose" module. It works with checkboxes, radio options and color selections and is compatible with Prestashop 1.6 and 1.7. Here is the link to the module in the addon store: https://addons.prestashop.com/de/product.php?id_product=47851