Leaderboard

Hello, I wanted to share a free module that I developed for PrestaShop and that can be useful for many merchants. 👉 JPresta Doctor The module lets you run a complete diagnosis of your PrestaShop store in just a few clicks. It runs more than 500 automatic checks to detect the most common issues: orphan data in the database inconsistencies after installing or uninstalling modules issues that may impact performance or stability unused images etc. The goal is simple. quickly know whether your store is healthy, without having to dig everywhere. 📥 Download the latest version and get more information: https://jpresta.com/en/prestashop-doctor-diagnostic-repair-clean-optimize If you have any questions or feedback, I will be happy to discuss. Have a nice day, Jérôme jprestadoctor-1.1.1-jprestadoctor.zip

Lot of SQL queries in PS are not optimized for huge data (history or lot of orders per day). Specially join queries with pagination are very poor. Let me give you a sample: This query takes several minutes if you have more than 100.000 orders, even on a dedicated database server 😞 SELECT o.`id_order`, o.`reference`, o.`total_paid_tax_incl` AS total_paid, ... FROM `ps_orders` o LEFT JOIN `ps_customer` c ON o.`id_customer` = c.`id_customer` LEFT JOIN `ps_address` a ON o.`id_address_invoice` = a.`id_address` LEFT JOIN `ps_order_state_lang` b ON b.`id_order_state` = o.`current_state` AND b.`id_lang` = 1 LEFT JOIN `ps_country` co ON co.`id_country` = a.`id_country` LEFT JOIN `ps_state` s ON s.`id_state` = a.`id_state` LEFT JOIN `ps_order_cart_rule` ocr ON ocr.`id_order` = o.`id_order` LEFT JOIN `ps_cart_rule_lang` cr_lang ON ocr.`id_cart_rule` = cr_lang.`id_cart_rule` AND cr_lang.`id_lang` = 1 LEFT JOIN `ps_order_detail` od ON od.`id_order` = o.`id_order` LEFT JOIN `ps_order_slip_detail` osd ON (od.`id_order_detail` = osd.`id_order_detail`) LEFT JOIN `ps_product` p ON p.`id_product` = od.`product_id` LEFT JOIN `ps_product_lang` p_lang ON p.`id_product` = p_lang.`id_product` AND p_lang.`id_lang` = 1 AND p_lang.`id_shop` = 1 WHERE o.`id_shop` = 1 AND o.`current_state` != 0 GROUP BY o.`id_order` LIMIT 0, 250 optimized query < 8 seconds should be something like: SELECT o.`id_order`, o.`reference`, o.`total_paid_tax_incl` AS total_paid, ... FROM ( SELECT `id_order` FROM `ps_orders` WHERE `id_shop` = 1 AND `current_state` != 0 ORDER BY `id_order` DESC LIMIT 250 OFFSET 0 ) AS filtered_orders JOIN `ps_orders` o ON filtered_orders.`id_order` = o.`id_order` LEFT JOIN `ps_customer` c ON o.`id_customer` = c.`id_customer` LEFT JOIN `ps_address` a ON o.`id_address_invoice` = a.`id_address` LEFT JOIN `ps_order_state_lang` osl ON osl.`id_order_state` = o.`current_state` AND osl.`id_lang` = 1 LEFT JOIN `ps_country` co ON co.`id_country` = a.`id_country` LEFT JOIN `ps_state` s ON s.`id_state` = a.`id_state` LEFT JOIN ( SELECT ocr.`id_order`, GROUP_CONCAT(DISTINCT cr_lang.`name` SEPARATOR ', ') AS distinct_coupons FROM `ps_order_cart_rule` ocr LEFT JOIN `ps_cart_rule_lang` cr_lang ON ocr.`id_cart_rule` = cr_lang.`id_cart_rule` AND cr_lang.`id_lang` = 1 GROUP BY ocr.`id_order` ) coupon_data ON coupon_data.`id_order` = o.`id_order` LEFT JOIN ( SELECT od.`id_order`, SUM(osd.`amount_tax_incl`) as refunded FROM `ps_order_detail` od LEFT JOIN `ps_order_slip_detail` osd ON od.`id_order_detail` = osd.`id_order_detail` GROUP BY od.`id_order` ) refund_sums ON refund_sums.`id_order` = o.`id_order` LEFT JOIN ( SELECT od.`id_order`, GROUP_CONCAT( CONCAT( '{"id_product":"', od.`product_id`, '","id_variant":"', od.`product_attribute_id`, '","name":"', REPLACE(COALESCE(pl.`name`, ''), '"', '\\"'), '","price":"', od.`product_price`, '","quantity":"', od.`product_quantity`, '"}' ) SEPARATOR ',' ) AS products_json FROM `ps_order_detail` od LEFT JOIN `ps_product_lang` pl ON od.`product_id` = pl.`id_product` AND pl.`id_lang` = 1 AND pl.`id_shop` = 1 GROUP BY od.`id_order` ) product_data ON product_data.`id_order` = o.`id_order` ORDER BY o.`id_order` DESC;

Since long time ago, I has been developing ecommerces in prestashop (and other platforms) and something needs to be said: Paid themes and modules are getting low quality, higher price everyday. Its totatly normal latelly to have Paid themes that doesnt work properly, or have modules on it from 4 years ago with security bugs (but theme has been updated on last days...) . Multiple modules that by default doesnt work in prestashop 8.1 (but they are announced as they should work). Themes installed that throws deprecated php instances over php 8.1 (to be honest, prestashop should upgrade to 8.2-8.3 before the EOL) Themes inheriting from posthemes that are copycats between them: same demos, same files, diferent names. Suport that only ask for ftp and login/password to access instean ask for information (its not only a bad practice. With the poor quality of their product after paying 60-70-80€ for them and crash, they ask you to have full access to your development shop to "solve" the problem. Prestashop members and prestashop community should say "stop" . Its totatlly normal the trustness of this platform is getting lower and lower: On last 2 weeks, we started 3 projects on prestashop and none of the modules installed worked as intended, and all of them in one or other way launches errors in screen or logs..... I know this message will be filtered, but at least the prestashop moderators should think about whats happening and why people are trusting in worst platforms only because the theme creators are pure greed people with a fake/scam products. (not all of them, but a lot of them for sure) S!

We tried to modify order, as client noticed that he does not want company name on invoice. After company removed, delivery costs were removed too from the order. I wonder why this stupid rule were created by developer and how to remove it from prestashop.

Instead of Captcha try Coludflare Turnstile. It appears to be more effective in blocking spam. A free module is available on GitHub.

Hello, I completely agree with you. I bought two themes this year and received "Deprecated" alerts for both, yet no comments mention any issues. The first theme was compatible with 8.2.x and the second with 9.0.x. The themes were recently updated, but these developers do nothing unless it's a critical error. It's high time PrestaShop cleaned up all these developers who publish such poor-quality themes, bordering on fraud.

Sí, va a entrar en vigor sí, ya somos de los pocos países de europa que no tienen algo similar, y muchos del este de europa funcionan así desde hace años. El tema está en que los políticos lo tenían muy fácil... solo tenían que hacer un comunicado y decir "ok, NO vamos a sancionar durante X meses", y listo (cosa que ya se venía comentando desde hacía meses). Pero NO, tenían que elegir la peor opción de todas: la que les permitía salir en rueda de prensa a colgarse una medallita, y así penalizan a todos los que intentan hacer las cosas bien y premian a los de la dejadez y los de "dejarlo todo para el último momento y aquí no pasa nunca nada"... Millones de euros perdidos en publicidad inútil, miles y miles de horas de desarrollo apresurado y de horas sin dormir de todo el colectivo de desarrolladores de este país, millones de euros de adaptación de dispositivos de hardware de los fabricantes de cajas registradoras, básculas.... Hay pequeñas tiendas que se han gastado un dineral inmenso para cambiar todo su hardware, y empresas que han tirado a la basura sistemas informáticos personalizados al dedillo durante décadas porque era imposible adaptarlos a tiempo. Pero sobre todo: Os aseguro que hay una enorme cantidad de negocios que directamente HAN CERRADO, gente a la que les quedaban pocos años para jubilarse y han visto imposible asumir (y pagar) tanto cambio y ya decidieron no continuar, e incluso mucho autónomo, mucho más joven, que se ha visto superado por la situación y ha bajado la persiana para siempre. A todos estos ¿qué les decimos? La base para que un país funcione económicamente es dar seguridad jurídica a quienes quieran hacer negocios en él, y en eso sí somos los líderes de europa: en tener una inseguridad jurídica al nivel de la peor de las repúblicas bananeras del mundo. En lo que a nuestro sistema se refiere, a seguir mejorando hasta 2027, y periodo de pruebas gratuito prolongado hasta finales de 2026.. y a los clientes que ya han confiado en nosotros les hemos informado por email de cómo vamos a actuar y al 99% les ha parecido bien.

ok, it works👍... Thanks again for the help

Hello, Ok, this makes more sense now. In your ps_facetedsearch module's configuration, in the template used, you are most likely having Search (experimental) checked in the Pages using this template: section. The problem seems to be the fact that ps_facetedsearch does not execute the actionSearch hook. If you uncheck that option, the default search class will be used in the search page, and this class does implement the hook, so you should start seeing the search keywords inserted into that table.

Mare sure the iframe parameter is allowed

Do oficjalnego wydania ich nowego modułu do PrestaShop 8 a znając życie może to potrwać jeszcze 2 lata nic nie zrobisz jeżeli wogóle planują wydać, dodam jeszcze że w samej 8 zależnie od szablonu lub samego serwera moduł miał często problemy. Możesz pomyśleć też o innej integracji np. furgonetka mają wtyczkę do PrestaShop 9 ogólnie ich developorzerzy prężniej działają z aktualizacją modułów po wydaniu nowej wersji praktycznie odrazu pojawia się moduł to też dobrze zapowiada kolejne wersje i przejścia do PrestaShop 10, 11, 12 nie będziesz czekał latami na moduł uprzedzę też odrazu pytanie o ceny jeżeli na apaczka masz lepsze ceny piszesz do furgonetki o tym fakcie i na twoim koncie ustawiają identyczne ceny wysyłek jak miałeś w apaczka a często ceny nawet są lepsze.

W większości przypadków moduł z PS 8 da się uruchomić na PS 9, ale to zależy jak jest napisany (czy trzyma się standardowych hooków, czy ma override’y i własne kontrolery). Najprostsza droga: Zainstalować moduł od Apaczka na kopii testowej PS9 Włączyć tryb debug i sprawdzić logi (Symfony / var/logs) – zwykle od razu widać, co nie pasuje Jeśli problem jest „kosmetyczny” (compatibility/version check), da się to szybko poprawić Jeśli są błędy w kodzie (override, niezgodne endpointy, stare klasy), to bez poprawek w module się nie obejdzie Alternatywy, jeśli Apaczka nie ma wsparcia dla PS9: integracja przez ich API (mały moduł „szyty na miarę”) użycie zewnętrznego narzędzia typu manager wysyłek/ERP, które obsługuje Apaczka i łączy się z PrestaShop (jeśli w Państwa procesie to pasuje) ewentualnie zostać na PS8 do czasu oficjalnej wersji modułu Jeżeli Pan/Pani chce, mogę to sprawdzić: proszę o kontakt w wiadomości prywatnej z wersją PS9, PHP, wersją modułu Apaczka i ewentualnym błędem z logów.

Cześć, Z tych danych najważniejsze jest to, że ma Pan bardzo wysoki TTFB (ok. 6 s). To oznacza, że problem jest głównie po stronie serwera/back-endu (hosting, PHP, baza, cache), a dopiero potem w „optymalizacji frontu”. Samo „minify” i WebP nie naprawi TTFB. Najprostszy plan działania: Potwierdzić, co generuje TTFB : WebPageTest (waterfall) albo Chrome DevTools → Network → dokument HTML: zobaczy Pan, czy serwer oddaje HTML po kilku sekundach. Włączyć prawdziwy cache W PrestaShop: Parametry zaawansowane → Wydajność: cache włączony, tryb debug off. Najlepszy efekt daje cache na poziomie serwera: Nginx fastcgi_cache / Varnish / Cloudflare (bo PrestaShop sam z siebie nie jest „full page cache”). Sprawdzić serwer PHP 8.1/8.2 + OPcache włączony, poprawnie ustawione PHP-FPM (process manager), HTTP/2, szybkie dyski. Włączyć slow query log w MySQL/MariaDB i zobaczyć, czy baza nie dławi strony. Wykluczyć winne moduły Na próbę wyłączyć moduły, które doklejają JS/trackery (cookie consent, pop-upy, analityka, slider, czaty, porównywarki) i sprawdzić, czy TTFB spada. Narzędzia, które realnie pomagają (zamiast zgadywania): WebPageTest (waterfall), Lighthouse, Symfony Profiler (w trybie dev na kopii), Blackfire lub New Relic (profilowanie PHP), MySQL slow query log. Jeżeli po włączeniu cache na serwerze TTFB nadal będzie kilka sekund, to praktycznie zawsze jest to hosting/konfiguracja PHP-FPM albo ciężkie zapytania do bazy/moduły.

Hi, Some reading material to help you secure your website. https://www.mediacom87.com/post/security/

Ciao, ho preso questo modulo e funziona benissimo per gli shop italiani....aggiunge i due campi sdi e pec al formato indirizzo. Per renderlo obbligatorio puoi chiederlo al developer nel caso non riesci a farlo..il modulo fá un'override della classe address per cui é facile alterarlo secondo le tue esigenze.

c'est normal le n° de tel est lié à l'adresse pas au compte. Vous l'aurez au moment de créer votre adresse.

Thank you for your suggestion. I will have a look and choose

dans votre fiche de description à la fin c'est marqué ça : Ce module s'installe suivant la procédure habituelle de PrestaShop et sera actif sur votre formulaire de contact sans besoin de configuration complexe. Installez le et utilisez le. donc pour moi c'est que pour le formulaire de contact ? non ?

Bonjour, Module installé, juste parfait, exactement ce que je recherchais, je vais gagner un temps précieux. Merci pour ce dev Juste une petite suggestion, l'ajout d'une case à cocher, qui le resterait, lorsque le produit est commandé chez le fournisseur.

La validation est en cours sur Addons, je propose déjà le module sur mon site : https://www.prestatoolbox.fr/transport-logistique/478-commandes-groupees-par-fournisseur.html

Prestashop's autoupgrade module works step by step, processing sql files that list what must be changed in the database for the next version. And at some point during that process it will cross the 1.4-1.5 border and add the root category. Those files are found in the /install/upgrade/sql directory (up to 1.7.0) and /modules/autoupgrade/upgrade/sql (after 1.7) Of course third party tools can choose to work in another way.

Bonjour, Je viens de passer sur votre site, il est en ligne ici.

Ha oui en effet, si je clique sur position, l'icone reviens bien, merci de votre aide

Jeśli w tym katalogu nie masz pliku custom.css to go utwórz i tam dodaj ten kod.

This is genuinely helpful, especially for anyone working with older PrestaShop setups. The way you broke down the on-page essentials makes it much easier to see what actually moves the needle. At fhseohub we often see merchants struggle with the exact issues you highlighted, so having a clean, practical checklist like this is a great starting point. Thanks for sharing your experience—it adds real value to the community.

you can run it through the PrestaShop validator to get some sense of the security and best pracatices https://validator.prestashop.com/

Gracias por el código, me sirvió estaba buscando algo similar.

Tampoco han hecho una campaña de información adecuada, ay muchos muchos muchos autónomos y pymes que no tienen aún ni idea, yo aun estoy informando a muchos, y otros han oído campanas pero no entienden nada. No es solo que haya gente que no haya empezado ha hacer cosas a ultima hora. También creo que las gestorías tienen mucha culpa por qué deberían informar bien a sus clientes dónde estos temas y no lo hacen ... En fin...

As was not having problems with WAMP maybe because my user was and administrator... For me it seems like permission problems. If you are doing this on local server just for testing, try to play with permissions. In your case, first i'll make user as admin and reinstall WAMP, try if it solves you issues, if not, make the directory, you install presta, permission settings 777 and try again.

Hello everyone, We are going to start offering our customers STL files for 3D printing. These are quite large files, around 200 MB per file, which are hosted on a Drive. The idea would be to provide the customer with a download link via email once they have made their purchase. Something like: ‘Thank you very much for your purchase, here is your download link’ Ideally, this link could also appear in the orders section of their customer profile, but this would be secondary. I don't see how to configure this in Prestashop 8.2. How could we do it? Does anyone know of a suitable module? Thank you very much for your help and best regards!

yes, install folder deleted. PS8 serves up the 'Maintenance' web page for both shop and back office. No ability to do anything. Frustrating!

I also added if (strlen($params['expr']) < 5) { return; } to avoid strings under 5 characters that aren't meaningful for the site.

Imagino que dentro de un año volveremos a leernos en este post...vaya panda nos gobierna

..it even writes two lines for research now 🙂 it seems he has to make up for lost time

I have tried both http and https. PS8 is installed without SSL, PS9 with SSL. PS8 gives me the 'We will be back soon' message under http, file not found under https. PS9 gives me file not found under both http and https My little HTML page works fine in http, file not found in https. I am missing something here!!

Hi Yes install folder deleted on both PS8 and PS9 folders. I have a TEST folder with a simple HTML Hello World page. Apache serves that up to me no problems.

@Mediacom87 : I already have such a module, which can wreak havoc if used without precautions @El Patron, Thanks, this seems like a viable solution. Unfortunately Prestashop have been a little shortsighted in their ambitions when it comes to scalability

Hello, displayHead is not needed. The statssearch module makes use only of the actionSearch and displayAdminStatsModule hooks Some things that you should watch for: 1. Check the `ps_hook` table and make sure that active is set to 1 for actionSearch. You can also add position 1 (to the same row) if it's not already set (SELECT * FROM `ps_hook` WHERE name = 'actionSearch';) 2. Make sure there are no overrides (or direct code changes) for controllers/front/listing/SearchController.php, src/Adapter/Search/SearchProductSearchProvider.php and modules/statssearch/statssearch.php. If there are, you should check the code for them in GitHub and make sure you are not touching the execution of the actionSearch hook

Activate debug mode or check error log to see the 500 error details

this module I've used several times for same exact issue, it works. https://www.aurone.com/blog/module-prestashop-archivebox-archiver-les-anciennes-commandes/

Hi everyone, is it possible to create a bundle containing products with a combination of the following: shoes ----> choose size and color socks ----> choose size and color shirt ----> choose size and color Will the bundle be priced at the total of the product prices? When purchasing, will the individual products be deducted? What happens if a customer purchases a single product from the bundle?

Dear Community, This morning, Monday 9th of September 2019, the forum has been unavailable during one hour, from 10:30am to 11:30am, Paris timezone. This upgrade was prepared and testing on an iso preproduction infrastructure in order to make it as smooth as possible. What has been done: Upgrade to version 4.4.6 of Invision, Installation of the Auto Welcome module in order to improve the on-boarding of new members Installation of the New topic information module in order to add guidance and tips to write better topics Tests that everything is fine The deployment of the new modules is still in work in progress and will also come with a new member group, "New-Members'", that will ease spam and troll filtering. It has been asked by forum moderators. If you would encounter any issue after this big maintenance, please write an answer to this topic or send me a private message via the forum.

Je suis chez https://www.planethoster.com (Offre Pro) et pas de soucis.

Bonjour, Ca m'est aussi arrivé sur 2 sites différents cette dernière semaine. De ce que j'ai pu en déduire voilà son fonctionnement : Il repère un module possédant une faille pour réaliser une injection sql. Ca peut être n'importe lequel, chez moi c'était 2 modules différents (un module interne spécifique à une boutique et le module smartblog) Une fois la faille repérée il effectue des requêtes SELECT sur la table INFORMATION_SCHEMA pour récupérer différentes infos dans la base de données Une fois ces informations récupérées, il connaît le nom de la base de données et peut commencer à y faire des UPDATE Il effectue une requête UPDATE sur nom de la boutique (le champ "nom de la boutique" dans Coordonnées & magasins) en y ajoutant le script softbylinux. Ce script peut ensuite être appelé le front mais également sur le backoffice, il semble qu'il se charge de récupérer tout ce qui est tapé (donc mots de passes, etc) Ce n'était pas le cas au début mais maintenant il semble que le nom de la boutique soit remis à sa valeur d'origine après quelques minutes, certainement pour rendre l'intrusion moins visible. Donc ce n'est pas parce que le nom de la boutique est normal que l'attaque n'a pas été faite. Si un mot de passe admin est récupéré, il se connecte et installe un module qui n'est visible que via ftp, mais pas depuis la page modules du BO. Vérifiez que vous n'avez pas un nouveau dossier "mymodule" dans le dossier "modules" de votre site. Si oui, regardez s'il contient un fichier suspect (chez moi myc.php). Si c'est le cas vous pouvez supprimer ce dossier. Je ne sais pas ce que fait exactement ce truc mais le contenu n'était pas joli joli, tout plein de références à du ssh, des mots de passes, etc Enfin, sur une des boutiques, il y a eu à priori une action manuelle, donc une personne se serait loggée en utilisant un mot de passe récupéré au préalable. Notre module de paiement par CB a été modifié pour passer en mode iframe, certainement pour récupérer les numéros de CB des clients. Coup de "chance", ce mode est incompatible sur notre boutique et donc l'iframe ne s'affichait pas et les clients ne pouvaient plus payer (ce qui nous a permit de comprendre qu'il y avait un soucis quelque part d'ailleurs) Le plus important est donc de consulter vos fichiers access.log et de chercher des appels à "SELECT" ou "UPDATE", en général toujours faits sur la table "ps_configuration". Si vous voyez des lignes sortir, vous devrez être capable de voir le module qui a été utilisé pour réaliser l'injection sql en regardant l'url au début de cette même ligne. La ligne en question ressemble à ça : /module/NOM_DU_MODULE/NOM_DU_CONTROLLEUR?p=61%27%3BUPDATE%20NOM_DE_LA_BASE.ps_configuration%20set%20value... Une fois la faille trouvée vous pourrez la corriger ou carrément supprimer le module problématique si vous le pouvez. Malheureusement ça ne semble pas être un module unique qui est source du problème donc chaque boutique devra chercher elle même le module responsable. Il faudra mettre à jour tous les mots de passes BO et par sécurité certainement ceux de la base de donnée et ftp également car je ne sais pas exactement ce qui peut être récupéré.

Ciao a tutti, devo creare una promozione 3x2, ovvero acquisti 3 prodotti e il meno caro è gratis. Ho creato la regola ma non riesco a capire come fargli applicare il calcolo dal prezzo di listino e non da quello scontato. Qualcuno mi può aiutare? Grazie

Hi there, This is my first topic here. I've been working with the PS webservice in order to create a SYNC system with an external ERP, and I would like to share my experience (if somebody is interested). I've also other scripts to add products (including images), etc. If somebody interested...let me know. Before using the script: - This is a LINUX bash shellscript (will not work in windows) - You have to install the "xmlstarlet" tools (apt-get install xmlstarlet in Ubuntu) - You have to install "CURL" (apt-get install curl in Ubuntu) - You have to create a config.inc file providing your PS webservice KEY and base URL for your SITE config.inc contents: WS_KEY=XYZABCDDJ5ERJTW81231231231231 BASEURL=http://YOURSITE.COM/prestashop/api After creating the config.inc file on the SAME directory as ps_edtProduct.sh you can use it on a regular console like this: Change QUANTITY for product ID=1234: ./ps_edtProduct.sh 1234 QUANTITY=120 Change PRICE for product ID=1234: ./ps_edtProduct.sh 1234 PRICE=120 Change WHOLESALE_PRICE for product ID=1234: ./ps_edtProduct.sh 1234 WPRICE=120 I'm experiencing problems while uploading images, they upload fine, but PS refuses to use the image as "main" image until I manually edit the product. Somebody having this issue? NOTE: I've uploaded the script renamed as .txt to avoid upload restrictions, please re-rename it after downloading

Me alegro! Un placer Ya ves que es más sencillo, rápido y eficaz

And of course, the screenshot of the validation of this post, from the moderators point of view.

Thank you guys for the answer. i had checked the theme translation, unfortunally there are not this sentence...only the following: ---You must agree to our Terms of Service before going any further!--- I agree to the [terms of service] and [revocation terms] and will adhere to them unconditionally---. Hm...

considero que ingresar a editar el codigo no es bueno, por que podemos cometer un error, estuve leyendo y encontre que si esta usando chrome para realizar la instalación es posible que una extensión bloquee el proceso, por lo cual, luego de encontrarme con el mismo problema, mi solución fue usar otro explorador para finalizar el proceso