Leaderboard

Merci Grok/ChatGPT^^

8.2, dar în ambele cazuri este mai bine să faci o instalare curată și să migrezi datele. În orice caz, dacă faci o instalare curată sau actualizezi, dezactivează modulele personalizate, treci la tema clasică și fă o copie de rezervă înainte de orice acțiune.

Ca marche si je réinitialise le module. Cdlt, Fred

Just fyi - the "Recently Viewed" module fetches the entire list of product ID's (no filters involved) into RAM 3 times and does a for-loop style walk through looking for matching ID's from the cookies. This is the memory flaw I mentioned and uses an undue amount of CPU time. With 3.4MM items, this required upwards of 1.5GB of RAM per visitor to display a list of a half dozen recently viewed items. Thanks to bot traffic these days, it is not uncommon to have dozens of simultaneous requests being made against the site which offer little to no return value. Cloudflare catches most of these, but it can't catch them all. The fix was simple - adding an IN clause to the select for IDs, but still required custom modifications. The 450 queries (reduced to around 150 with caching enabled) the software executes are mainly to determine all of the feature, layout options, and customizations a site uses. This issue is not related to catalog size.

I appreciate the suggestions, however disk I/O wasn't any part of the issue. Any software which fires 450 queries at the database server and consumes 1.5GB of RAM per visitor to display a product detail page has flaws that storage performance and database configuration tweaks won't solve. This was the results of the profiling done against the default install of PrestaShop with their catalog loaded. I submitted a pull request to deal with some of the initial memory issues I ran into, but the query counts are inherent in the way Presta's code is written. Some of these issues can be partially mitigated by reducing the functionality of the site, but that was honestly the initial appeal of using Presta. In this case, I am the agency working with the customer to update their site / software. I have years of experience in database administration, working with systems much larger than 3.4 million records. Some of my other customers have databases with billions of records and terabytes of data. They, however, are in the tech industry, not the lawn equipment industry. This was merely a test case for PrestaShop as it might have been a simple solution for their shop. The test systems used to initially profile the software had NVMe storage, hundreds of gigabytes of RAM available, and each test instance could be allocated dozens of cores if needed. However, the target hosting platform can not contain these sorts of specs as it is cost prohibitive to allocate such resources... unless self or co-locating the hosting. They do not have the technical resources for this. As mentioned previously, the solution ultimately chosen was to create a custom site. The resulting code and software have no problems querying the customer's catalog on much more modest hardware platforms. This is not a knock on PrestaShop. As I mentioned, I really enjoy the software and have used it for other projects. It just wasn't a good fit for this particular customer's needs. There is no such thing as a truly one size fits all e-Commerce solution. Aside from the size of the catalog, their needs included things like large supersession chains, product substitution lists, and the ability to lookup no longer available parts for cross referencing. These are not part of Presta's base functionality and would have required additional custom modules to be written. There were simply too many modifications needed to make it suit the purpose of the site.

PrestaShop 8.2 vs 9.0: WebP (and AVIF) — what actually works • In PS 8.2 there’s a native WebP toggle, but it’s experimental. Path: Advanced Parameters → New & Experimental Features → Enable WebP. Then go to Design → Image Settings → Regenerate thumbnails (All images). • How it behaves in 8.2 – URLs may still show .jpg/.png, but browsers that support it get image/webp. – Most thumbnails convert; some originals remain JPG/PNG. – Requires GD or Imagick with WebP enabled; otherwise PS quietly falls back to JPG/PNG. – Some themes/modules don’t love the MIME swap. • Verify quickly – DevTools → Network → click an image → Content-Type: image/webp. – Or terminal: curl -I "https://yourshop.com/img/p/1/2/12-large_default.jpg" | grep -i content-type • Works in 8.2: regenerated thumbs, WebP delivery in supported browsers. • Limits in 8.2: no AVIF, inconsistent coverage, confusing file names; many shops still use an optimizer module for full coverage & fallbacks. • PS 9.0: WebP becomes first-class (not experimental), adds AVIF, and is more consistent across all image types. Full guide (steps, checks, tips): 👉 HERE

Acabo de desarrollar un módulo para n8n que permite interactuar fácilmente con el Webservice/API de PrestaShop, abriendo un mundo de posibilidades en la automatización de procesos eCommerce. Si quieres una guía visual de instalación, funcionamiento y ejemplos prácticos de flujos de trabajo listos para importar en n8n, este video te interesa: 👉 El proyecto es open source y está disponible para colaboración: 👉 https://github.com/prestaalba/n8n-nodes-prestashopadvanced La automatización no es solo ahorrar tiempo, es abrir nuevas oportunidades para crecer. ¿Te sumas?

Hi, i'll add a few more tips to what was written by El Patron. This is a bug of new Ps9 that will be fixed i think in the end of August with new release. Actually the code of the module is updated!!...but in backoffice it continue to show the message ..well to fix this you have to update the module and than reset the module and you will see the new version:-) https://github.com/PrestaShop/PrestaShop/issues/39151 Cheers

Hi, you need to delete folder var/cache/prod and var/cache/dev. And also in database replace old domain with new one but not only ps settings, but all url in database like cms page or product description that contains links. Example move from dev.mydom.ext to www.mydom.ext in SQL dump file replace all occurrences of dev.mydom.ext by www.mydom.ext

Salut! NU UPGRADE. Fa-i site-ul de la 0, recomandarea mea, mergi pe ultima versiune de la 8. Dupa aceea, preluare de date din cel vechi in cel nou. (comenzi, cosuri, clienti....etc).

Solved! Posting the fix in case it can help somebody in a similar situation. There was an update of MariaDB on the servers, and this issue might have been related to it. Using the debug mode on the backend page it threw an 500 error related to the blockwishlist module. Hosting support fixed it. After that the dashboard was accesible but the 500 error kept popping up in the order panel, related to the paypal module. That got fixed when i uninstalled it. I assume it will get fixed when I get the updated version to reinstall. After that I cleared the prestashop caché using the terminal in cpanel. In any case, the error was related to some updates on the server and some modules broke and crashed the dashboard and other pages on the backend.

I think PS1.6 supports PHP7.1 only, while Prestashop8 requires PHP7.2 onwards. So I believe a direct upgrade will not be possible using the 1Click upgrade.

Buenos días, Con todo el respeto, pero creo que estás equivocado o leyendo mal. En primer lugar, aquí no se está hablando de una solución gratuita, si no de un modulo de un pago único. En segundo lugar, has visto los precios de esas "míseras" subscripciones? Eres autónomo o una pyme? Si lo eres sabrás que hoy en día para todo hay que pagar una "misera" suscripción, suma suma suma y hablamos de lo que duele otra "misera" suscripción. En tercero, todo lo que sea impuesto por ley y que obligue a hacer algo debería estar subvencionado o ser gratuito ya que es una obligación, no un derecho al que acogerse si uno quiere, por lo que el propio gobierno debería poner a disposicion las herramientas de una forma sencilla y gratuita para que todas las empresas, incluidas autónomos y pequeñas empresas, puedan ajustarse a la normativa sin arruinarse en el camino. Y es que no es una "misera" suscripción más, es que esto es constante y no deja crecer ni respirar a autónomos y pequeños comercios entre unas cosas y otras... "Acaban" de salir dos normativas, la factura electrónica y la obligatoriedad de que las webs dispongan de un "simple botoncito" que permita cambiar todo el estilo de la web y alguna que otra funcionalidad para que sea accesible a todos los públicos, y cuando no es una es otra, y hay que pagar por todo (a nivel fiscal, a digital, a nivel social... Dentro de poco hasta por respirar), y si suben los precios pierden clientes por k el servicio/producto es caro, y competir con las grandes empresas ya es casi imposible y lo que no está impuesto hay que hacerlo "obligatoriamente" si quieres salir adelante. Mi madre, por ejemplo, que tiene una empresa familiar de limpieza de portales con tres empleados y que tiene un crecimiento muy moderadoDespués de todos los pagos (IRPF, autónomos, material, sueldos, seguridad social, iva, gastos de web, empresa de riesgos laborales, empresa de seguro laboral, abogado, gestoría, ditgitales, "míseras" suscripciones, etc etc etc) después de un año de trabajo tiene un beneficio neto de 3000€ y por ello tiene que pagar 900€ de impuesto de sociedades de ese beneficio... Pues si, cualquier nueva "misera" suscripción duele y más si es por algo impuesto. Y ella intenta no defraudar, ser legal y lo declara todo, pero es que de verdad que no lo ponen fácil, viendo esto luego nos sorprendemos de que haya empresas que hagan cosas en B ... Y si te dejas un pago sin hacer por qué no tenías dinero te acribillan a intereses (k ni un banco usurero llega a ellos) y como no pagues es tu perdición y a las grandes empresas le perdonan más de la mitad de las deudas que tienen para que paguen algo... Mucho apoyar al comercio local y todo eso que queda tan bonito pero luego a la hora de la verdad ....

https://prestaheroes.com/blogs/mysql-optimization/how-to-calculate-the-right-innodb_buffer_pool_size-for-prestashop-on-mysql-8-0

Hello papich, as i wrote above in the topic you have to update the module in the backoffice clicking on the upgrade button....than when you receive the "green" message you have to reset the module ( click on "down-arrow symbol and choose reset).Clean browser cache and you will see new version in module list. Keep in mind that if you have particular configuration in some modules you lose it, so make a copy of configuration.

Bonjour, chez moi en local php 8.4 presatshop version 9 fraichement téléchargée et installée aucun module ne se met à jour pourtant j'ai bien le success message.

Great, now we have another error, but the previous one seems to be solved 🙂 Check if there is a file in your theme directory: layouts/layout-full-width.tpl The full path will be something like this: /public_html/your_shop/themes/classic/templates/layouts/layout-full-width.tpl If it's not there, let me know if you have any modifications to the classic theme. Is it “original”?

This error indicates a problem in the ps_eventbus module (the action column is missing). First, check the table to see if the ACTION column exists using a query (e.g., via phpMyAdmin): SHOW CREATE TABLE ps_eventbus_incremental_sync; The table structure should be as follows: If not, add it with the query: ALTER TABLE ps_eventbus_incremental_sync ADD COLUMN action VARCHAR(50) NOT NULL; Remember to adjust the ps_ prefix to the one used by your store. Alternatively, try disabling the ps_eventbus module completely and see what happens. If the problem is solved, consider reinstalling this module (uninstall and reinstall) - if you need it at all.

Bonjour, j'aimerais savoir comment forcer le préfixe www. devant mon nom de domaine ? Les directives sur .htaccess créent des "too many redirect" Les impressions écrans pour changer l'adresse de la boutique ne sont pas les mêmes que les miennes, et j'ai peur de mettre www. et que si quelqu'un viennent sans www. ca ne marche plus. Merci de votre aide.

Aquí hay muy poca información para poder ayudar, así que es difícil saber exactamente por qué de repente tienes 1 millón de URLs indexadas. Decir que tu robots.txt es perfecto es dudoso — en realidad, la navegación facetada (filtros) casi siempre es la culpable de este tipo de explosiones de URLs en PrestaShop. Aquí te dejo un robots.txt mínimo enfocado solo en bloquear los parámetros de facetas más comunes (ordenar, filtros, paginación) que generan infinitas URLs duplicadas: User-agent: * # Bloquear parámetros de navegación facetada (causan explosión de URLs) Disallow: /*?orderby= Disallow: /*&orderby= Disallow: /*?orderway= Disallow: /*&orderway= Disallow: /*?selected_filters= Disallow: /*&selected_filters= Disallow: /*?n= Disallow: /*&n= Disallow: /*?p= Disallow: /*&p= Esto no bloquea tus productos o categorías principales, solo las variaciones infinitas de filtros que Google no debería indexar.

¿También indexas URLs como atributos, etc.? ¿Qué muestra GSC sobre esas URLs?

Ive just re-installed this because I had to remove due to a bad bug. After installing this one, its working, but there is some error in the css file "payments.css" This is how it looks So you need to add this css to your custom.css /* CHECKOUT PROCESS */ .ps_checkout-payment-option label { display: flex !important; } then it looks like this If you share your url then maybe a little bit of css changes will resolve your issue.

If you send people directly to a $29 e-book page, most won’t convert. The reason is simple: they don’t know you yet, and their past purchases have probably been from well-known authors at much lower prices. So the trick is not to push the full book right away, but to start with a small, irresistible offer. Something like a 10-page “mini version” priced at $1.99. It’s cheap enough to be an impulse buy, and it gets you past the biggest barrier: having their card on file and earning a first layer of trust. The real profit comes after that first step. Instead of sending them to the thank-you page, you redirect them to an upsell page. That’s where you offer either the full version of the e-book (hundreds of pages) or even a bundle of five strong titles in the same niche for $29.99. Some people will say yes, and that’s great. Those who say no shouldn’t just be dropped, this is where you introduce a downsell, the same offer but with a 20 to 30 percent discount (for example $19.99). Either way, whether they accept or decline, you then move them to the thank-you page. This kind of funnel works because it matches buyer psychology: low friction entry, then higher ticket offers when trust has been built. The upsell and downsell stages are where you recover ad spend and generate profit. Speaking of ads, since you’re targeting global markets, I’d suggest splitting the budget roughly 70 percent on cold traffic for the $1.99 offer, 20 percent on retargeting (people who clicked or almost bought but didn’t), and 10 percent on awareness/testing creatives. A starting daily budget of $50 to $100 is enough to gather data, and from there you can scale by reinvesting part of the profits. It’s not about the $1.99 sales at all, it’s about building a funnel that takes someone from “never heard of you” to “just spent $30 with you” in a single flow. That’s the power of this strategy.

Hola a todos, vemos que en junio de 2025,estamos obligados a enviar las facturas electrónicamente a la hacienda tributaria, por sistema verifactu. No estamos encontrando ni un solo modulo para Prestashop, solo Apis externas que hay que añadir todas las facturas. ¿Alguien sabe de un modulo disponible? Muchas gracias y saludos

@El Patron Thank you!

https://app.screencast.com/XHVH2nsI5pFtB what happened? did you dahs all your dreams? if you were using the theme compatible with smart blog...well bad choice, I know that theme all to well...old...ugly and outdated. one should only use theme with that supports 'elements', that theme has not been upgrade since before electricity. Don't give up. Yes, it works in PS9. But long-term, developers should prefer Symfony’s slugger service (or Transliterator) since that’s the modern direction.

Hi, I saw many and different instruction on what exactly one should do in order to change the domain name of Prestashop. I'm running Prestashop 1.6 and have installed on temporary hosting a new Prestashop 8.2 version which is ready for use. I want to erase old Prestashop and move current 8.2 to the main host.Now for 8.2 I use subdomain.My question is which are the official steps/instruction which Prestashop developers give for doing this? .htaccess, friendly URL, links etc. Thank you in advance

Par défaut, PrestaShop n’offre pas d’option dans le back-office pour limiter la longueur des titres de produits dans la liste du catalogue. Donc, il n’existe pas de réglage natif. La colonne “Nom du produit” prend toute la largeur que le titre occupe, ce qui peut vite casser l’affichage si tu as des titres très longs. Voici le style css qu il faut ajouter : table.table td.column-name { max-width: 250px; /* largeur max de la cellule */ white-space: nowrap; overflow: hidden; text-overflow: ellipsis; } Si tu ne parviens pas à faire la manipulation je peux t assister.

Avec grand plaisir envoies les moi en mp. Ca sera plus efficace.

welcome to community tested looool ps_checkout has been a nightmare, I made a lot of money with client intakes of broken checkout...we just removed it...you should consider the same unless ps has no other option for the payment gateway you use.... Yep—this is a real bug in the latest ps_checkout update (rolled out around Aug 22–25, 2025). Multiple shop owners are reporting the exact same crash on the Back-Office/FO with this stack trace pointing at the module’s English XLIFF file: modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf (XLIFF parser: “source element not expected”, Error 1871). prestashop.com+1 Here’s the quickest way to get the site back up and keep ps_checkout usable: Restore access (if you’re locked out): via FTP/SSH, temporarily rename the module folder: modules/ps_checkout → modules/ps_checkout.off (site comes back). prestashop.com Target the bad file only: put the module folder name back to ps_checkout, then delete this file: modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf. Several users confirm the module will run without that file. prestashop.com Clear cache: delete var/cache/prod (and var/cache/dev if present). Reload Back-Office and test checkout. Why it breaks (short version) The shipped en-US XLIFF is not schema-valid for what Symfony’s XliffFileLoader expects in PS 8/9—hence the “[ERROR 1871] … source element not expected” crash during cache warm-up. Removing or replacing that one file avoids the fatal. prestashop.com let us know how that works for you!

Tenemos el mismo problema con mi proyecto. ¿Alguien puede ayudarme a resolverlo?

Pardon me for the google translation: Hallo an alle Deutschen softwareentwickler von Prestashop! Sie können diesen fehler beheben, indem sie diese zeile löschen: modules/ps_checkout/views/css/payments.css:434 display: inline !important; In case the translation doesn't make sense, you can fix this error by deleting this line: modules/ps_checkout/views/css/payments.css:434 display: inline !important;

Bonjour @BrunsonDid, La version compatible Prestashop 9 devrait être mise en ligne d'ici la fin de la semaine, elle est prête 😉

Dziękuję wszystkim za pomoc - namierzyliśmy moduł, który powodował problem. Będziemy diagnozowali już bezpośrednio przyczynę tam.

Bonjour à tous ? Vous n'êtes pas sur le bon forum... Avez vous vidé le cache ? Avez vous vérifié que votre version PHP est la meme que sur l'ancien serveur ?

The error shows that the backup namespace is not available in your CLI. The safest way is to handle backups directly on the server side using tools like mysqldump for the database and a simple archive command for the files. This is more reliable than depending on PrestaShop’s Upgrade Assistant which is not always stable for backups.

Ya tenemos un módulo gratuito para configurar Webhooks en PrestaShop 🚀 que nos permite enviar notificaciones a sistemas externos en tiempo real ante eventos ocurridos en nuestra tienda (creación, actualización o eliminación de cualquier entidad). Es una versión muy simple para comenzar, con mucho campo para mejoras. Las contribuciones son bienvenidas 😉 https://github.com/prestaalba/ps_webhooks Les dejo video con una pequeña muestra de lo que se puede hacer a partir de ahora usando este módulo.

The The sender (ie in Shop parameters / Contact must be the same) sample with smtp user [email protected]

You will never believe it When we had the same problem, the last resort working solution was to restart the Wifi box… and it worked somehow

How to replace your existing PrestaShop domain with your upgraded shop If you’ve built your upgraded PrestaShop 8.2 on a subdomain (e.g. new.mysite.com) and now want it to take over your main domain (e.g. mysite.com), here are the recommended steps you should follow. This process ensures you retire the old 1.6 site cleanly while putting your upgraded shop live on the existing domain. 1. Plan redirects first To protect SEO and ensure visitors don’t get lost, set up a 301 redirect from your temporary subdomain (new.mysite.com) to your main domain (mysite.com). You can do this in your hosting control panel or with .htaccess rules. Additionally, there are some good redirect management modules available on the official PrestaShop Addons marketplace. These can make it easier to manage complex redirects, track hits, and avoid SEO penalties. Having your redirect strategy ready before the move ensures Google and customers are sent to the correct place immediately. 2. Archive your old 1.6 shop Instead of deleting it outright, create a subdomain (for example archive.mysite.com) and move your PrestaShop 1.6 files + database there. This way you still have access to historical orders, customer records, and references if you ever need them. Once the 1.6 shop is safely archived, you can remove the 1.6 files from the main domain root to make room for your upgraded shop. 3. Put your upgraded shop on the main domain Use FTP or your hosting file manager to move all files from the upgraded 8.2 shop’s subdomain directory to the root directory of your main domain. If your host allows, you can simply change the domain’s document root to point to the subdomain folder instead of physically moving files. 4. Update database domain settings Log into phpMyAdmin (or any MySQL tool). Go to your shop’s database. Open the table ps_shop_url (replace ps_ with your prefix if different). Update the fields: (without prefix https://) domain → mysite.com domain_ssl → mysite.com physical_uri → / (Make sure there is no new. or subfolder path left.) 5. Clear cache and regenerate .htaccess Delete the contents of /var/cache/prod/ and /var/cache/dev/ (if they exist). In your back office, go to Shop Parameters > Traffic & SEO. Temporarily turn off Friendly URL, save, then turn it back on and save again. This will regenerate a fresh .htaccess with the correct domain rules. 6. Update configuration files (if needed) Most likely, since you are moving from a subdomain on the same hosting account, the database name, user, and password are already correct and you don’t need to change anything. But if you do need to check or update them: For PrestaShop 8 → open /app/config/parameters.php For PrestaShop 1.6 → open /config/settings.inc.php Inside these files you’ll see the DB settings (database_name, database_user, database_password, and database_host). 7. Test and fix links Visit the site on the main domain and check the homepage, category pages, product pages, and checkout. If you see links still pointing to the old subdomain, clear browser cache and PrestaShop cache again. Also check your sliders, banners, and custom modules — sometimes they store fully qualified URLs (like https://new.mysite.com/...) instead of relative paths. Update these manually in the back office if needed. Summary: The official way to replace your existing domain with the upgraded PrestaShop is: plan 301 redirects (manual or via a module) → archive 1.6 to its own subdomain → clear main root → move 8.2 shop → update ps_shop_url → clear cache → toggle Friendly URL to regenerate .htaccess → confirm DB settings → test links (including sliders/banners with hard-coded URLs).

Honestly, if we take a closer look, PrestaShop has come a long way, especially since it was sold to that big logistics group. With V9, you are not really getting flashy new features, it is more about cleaning up the code, upgrading to the latest Symfony and PHP, and making sure the open source core stays maintainable for the long run. From what I have seen, their vision for PrestaShop 9, while also working on 10 in parallel, is to make it truly platform agnostic so whether you are running on AWS, Nginx, Apache, or pretty much any hosting provider, it just works without headaches. Of course, each new release means agencies and developers have to spend time adapting code, testing, and stabilizing everything, which is no small task. That is actually why we built our own theme and over 50 modules designed to work together flawlessly. Now, when we take on a client, we can cover 80 to 90 percent of their needs right out of the gate without worrying about compatibility issues.

Hola, Por lo que estoy viendo de momento todas las soluciones que se están ofreciendo son "APIs intermedios de pago" que requieren suscripción.... sin embargo el API proporcionado por la administración es un API público y gratuito (requiere autenticación con certificados, etc...) pero nada que impida desarrollar un módulo para Prestashop que se integre directamente con los APIs públicos de la administración. No queda mucho tiempo, no creeis que habrá algún desarrollador que se decida a desarrollar un módulo que no requiera suscripción? Me dan ganas de ponerme yo con ello.... (pero tengo muy poco tiempo...) saludos, Roberto.

As you will have noticed the Trustpilot scores for Woocommerce and Shopify are even lower. Only Magento scores slightly better. Ecommerce software has lots of options and allows on top of that plugins/modules. In such complexity things can easily go wrong. The Italian owner of Prestashop is a bit too aggressive commercially and you see that back in the reviews. Whether you will find it worth to get into it depends on what kind of development you like. Prestashop runs since version 1.7 under the Symfony framework. The supported business data have since then hardly changed. Almost all their development focuses on the software structure and to a lesser extent the backoffice. I assume they try to please some big companies. The problem is that this makes the code more and more complex what makes debugging problems harder. If you have a look at the software you should also look at Thirtybees. That is a fork of Prestashop that maintains the PS 1.6 structure of the Prestashop code and has updated it to run with the latest PHP version. A few years ago this forum was much more busy. On Builtwith you can see that Prestashop is becoming less popular rather quickly. I see a few reasons. They have made it very hard to install the software under Windows - and that is where many people try there ecommerce software for the first time. In 2021 Prestashop was bought by an Italian company - MBE Worldwide. In the process the software was split. There is now an opensource project that maintains the software core and there is MBE that provides a number of extra modules. For my taste this hasn't worked out very well. The opensource project is dominated by Linux nerds and could use some common sense from commercial people and the MBE modules tend to be not stable enough. The commercial pressure of MBE doesn't help either.

It appears to be: The SmartBlog module has not been updated to be compatible with PrestaShop 9.0. Possible Solutions Update the SmartBlog module: Find an updated version of the module that is compatible with PS 9.0. Contact the module developer to request an update. Temporarily modify the code (workaround): You could edit smartblog.php and replace Tools::link_rewrite() with the equivalent method in PS 9.0 (possibly Tools::str2url() or similar). Deactivate the module: If it's not essential, you could temporarily deactivate it until a permanent solution is found.

If no one had updated to the newest version the insecurity would not have taken so many victims. That is a good idea. I wouldn't be too sure that Prestashop has your best interest in mind. Their security holes play neatly into their SaaS plans. Grandmaster is a forum title nothing else. It means I must have done something right.

You don't debate, you simply suppress what you consider to be a problem. That a free module is not perfect bothers me much less than the thousands of copies of modules doing the same thing, or that paid modules are so poorly developed and insecure, or that themes are filled with modules without receiving the same control constraints, and so on. You criticize the French, but surprisingly, it is still this community that offers real community solutions to security problems in its universe, and of course for free. So I still think that by accompanying the good will to make free modules available can be a benefit for the whole community.

Volviste por el redsys?

awesome. Thanks.

This problem is most of the times related to SSL issues. If you have HTTP to HTTPS redirects enabled while there is some other setting which redirects a https request to an http webpage, hen you will get this error. For example, if you have HTTP to HTTPS redirects enabled, but you have a setting in .htaccess which redirects like this: Redirect 301 * http://<DOMAIN_NAME>.com/ Or if you see some other settings in there which redirects to a http page. That's most commonly related to this issue in my opinion. Next is if you for example use Cloudflare. Cloudflare has 4 SSL options: 1. "Off (Not Secure)" 2. "Flexible" 3. "Full" 4. "Full (Strict)" What SSL setting should I use? This setting controls how Cloudflare’s servers connect to your origin for HTTPS requests. We recommend enabling the Full SSL (Strict) setting if possible. Common use cases for each are: Off: No visitors will be able to view your site over HTTPS; they will be redirected to HTTP. Flexible SSL: You cannot configure HTTPS support on your origin, even with a certificate that is not valid for your site. Visitors will be able to access your site over HTTPS, but connections to your origin will be made over HTTP. * Note: You may encounter a redirect loop with some origin configurations. Full SSL: Your origin supports HTTPS, but the certificate installed does not match your domain or is self-signed. Cloudflare will connect to your origin over HTTPS, but will not validate the certificate. Full (strict): Your origin has a valid certificate (not expired and signed by a trusted CA or Cloudflare Origin CA) installed. Cloudflare will connect over HTTPS and verify the cert on each request. And last one you can check is for when you get this error while you did just install Prestashop. 1. Try to log in to the backend via: https://<my-domain.com>/Backoffice/index.php 2. In PrestaShop Backend, click Shop Parameters (under Configure) > General. 3. Click "Yes" next to Enable SSL and click Save to apply the changes. 4. Then click "Yes" next to Enable SSL on all pages and click Save to apply the changes.

Why bumping such an old topic :-) And link you provided, generator was good but last commit was 2 years ago and it says for version 1.5. Some people use official generator https://validator.prestashop.com/generator