Leaderboard

Bonjour, Depuis la version 9 ( toujours en préparation ), PrestaShop ne publie pu un zip sans ses modules ( checkout, account, gamification ... ) Sur presta.zip vous pouvez retrouver les versions du projet open source sans tous ces modules préinstallés Enjoy

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.

This is very first version of the module, it will be developed and new verification options will be added. Currently, the module only checks two things, it compares name and surname. If both are identical, it does not allow you to create an account in the store. Module aslo check letters in firstname and lastname, if it's unusual it will also block spammer to create account. Accounts like below will not be created in store. ***New version 1.0.1*** in version 1.0.1 there is new option checking letters, lowercase and uppercase. Firstname or Lastname like: mcdonald, Mcdonald, McDonald, MCDONALD, mCDONALD, mCdONALD are valid and allow to create account, but Firstname or Lastname like: McDoNald, mCdOnALD, MCDonald, McDonalD etc. aren't valid and user can't create account. It also should block account like that: ***New version 1.0.2*** In this version was added verifictaion for firstname and lastname that their are same even then some letters are lowercase or uppercase in fistname and not in lastname. Before user with first and last name like: Andrew andreW was able to create account, now he will be blocked. If you have any suggestions for validating a customer account, please post below. All suggestions will be considered and the best ones implemented into the module. It should work with prestashop 8.X and lower like 1.7.8 not tested with lower version then 1.7.7 ***New version 1.1.1*** Added configuration page to module. wfeuserverification1.0.0.zip wfeuserverification1.0.1.zip wfeuserverification1.0.2.zip Version 1.1.0 and newest was not tested, you install it on your own risk! wfeuserverification-1.1.0.zip wfeuserverification-1.1.1.zip

Warning! This module is likely unsuitable for most standard stores. It was created with small businesses, manufacturers, and artisans in mind, especially those frequently selling similar products under their own brand. The module integrates with ProductAdditionalInfo and ProductExtraContent, displaying text configured in its settings. The module's configuration for a specific product displays individually entered data for that product (overriding the general settings). In theory, you can configure all products in any store this way. However, in practice, for most stores, I would recommend paid solutions. 😉 gpsrproductinfo.zip

You should not set the default category to "Home." Instead, create a main category for your products (e.g., "Catalog") and organize products into relevant subcategories. This will improve navigation, site structure, and SEO. The default category is for technical purposes, not optimization.

@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

Anti-Spam, Anti-Bot, Anti-Brute-Force, Block Unwanted Bot and Spammer Traffic The module allows you to protect registration and login forms from bots. Limit the number of login and registration attempts. Module protect and limits the use of contact form, newsletter registration form and modules 'productcomments', 'iqitreviews'. Also, the module detects and ban more than 90% of the simplest bots. It is possible to manually block an IP and Email addresses, as well as exclude blocking. The module keeps a log of connection attempts and a log of entered data. After install, module creates 2 tabs in BO Customers tab. SS Triggers - phrases and words for contact form and 'productcomments', 'iqitreviews' modules (empty table after install and create own list). SS Actions - attempts log table with controls (view, edit, delete). Developed for 8.X but may work with 1.7.8+ (Reported: works on 1.7.8.3) The module will NOT work with versions below 1.7.8.3, perhaps in the future... WARN: This module may not works if you have specific modules for login, registration, contact pages or specific modules for cache. This module uses the standard $_SERVER/ENV - php/apache vars and Cookies. Module not works if you have installed some caching module who change standard server parameters. Please write me if you have problem with module and I will try to adapt it for your site for module correct work. Download simplesecurity.zip (Always latest version.) ~=DONATIONS ARE WELCOME=~ About updates please read this topic. Also check my other modules: HTML Minifier (lightweight module)

"Featured Categories on Home Page" module (hook 'displayHome'): Header + additional description (multi-languages) Displays images of the Categories Dynamic counter of active products in the category Counter of "selected categories" Compatible with PrestaShop 1.7 - 8 Language versions: EN (PL and soon more languages...) Screen: === mkd_categories_homepage.zip

@202ecommerce Thanks for delivering the PS9 version! I know that must have been a lot of work. https://addons.prestashop.com/en/payment-card-wallet/1748-paypal-official.html

As you may have noticed Prestashop is no longer an independent company. The last two years it has been part of a bigger company. This company increasingly pushes to get more revenue from Prestashop. The advertising on this forum is the most visual symptom of that. Another symptom is that there are now two versions of Prestashop 8.1.1 to download. On the Prestashop website you can download the "PRESTASHOP EDITION BASIC" with a size of 114 MB. On Github you can download a version of 80 MB. The difference is that the "Edition Basic" contains 11 modules extra. Here is an overview: - commercial partners (klaviyopsautomation, ps_checkout, psxmarketingwithgoogle, ps_facebook, mbeshipping) - gamification - ps_mbo: Marketplace in the Back Office: the second entry in the admin Modules menu. - ps_accounts: leads your login via the Prestashop website. Problematic when you need to have more than one login account ("employee"). When you find yourself unable to update other modules ("Could not perform action update for module undefined") this module may be outdated. You can circumvent this module by clicking on the small link to an "other" login method. - ps_edition_basic: I am not sure what it is for. It is not important. It is a major source of problems as it requires PHP 8.1 and thus torpedoes compatibility with older PHP versions. In PS 8.1.5 and 8.1.6 you may see just after the installation a warning that ps_edition_basic needs to be updated. In my case I chose to do that and the call failed. I suspect that it somehow requires you to have an account on the Prestashop website. Unfortunately I don't know an url where you could download this module in order to install it yourself. In the Modules page in the backoffice the module is not marked as needing an upgrade. Anyway, you can click the warning away and use th shop without upgrading the module. - ps_eventbus: this is some software library for sequencing tasks. It is used by other modules, including ps_facebook. For that reason removing is not recommended. It creates a ps_eventbus_incremental_sync database table that can grow very big and may need to be truncated sometimes. Search the forum for more info. - ps_metrics: provides some statistics and info about your shop. This is a Prestashop service. The first month is free. After that you have to pay. - psassistant: this module was added in 8.1.2 a few weeks after the version had been introduced (yes, Prestashop makes small changes to a release in the course of time). I suppose that it enables Prestashop to give you remote support. The core version of Prestashop is maintained by the Prestashop project with Github https://github.com/PrestaShop. The extra modules are maintained by the Prestashop company with Github https://github.com/PrestaShopCorp During an upgrade always the Github version is used. The Prestashop modules must be updated separately. If you want use an older version than the latest you can find it here. This page shows also the XML file that you will need for the 1-click upgrade module. If anyone has additional information, please write here below. If you want to install Prestashop with older PHP versions you should either take the Github version or take the Edition Basic version and allow it to fail the first time. You can then delete the ps_edition_basic module under the Modules directory and then click the link to retry the installation. For Prestashop 9 the Github version is much harder to get. See my reaction #23 below for details.

Changes the order reference from a random string to a random number or order ID. This module was used by many shops, but deleted some time ago from this forum by one nasty user. People keep asking me for it, so here it is reuploaded. Still works for Prestashop 1.6, 1.7 and 8.0. gmnumeric_v_1_2_0.zip New version - to make sure the new override is applied, I recommend to reinstall and reconfigure the module. gmnumeric_1_2_1.zip New, override free version for PrestaShop 8.1.0 and above. Please uninstall and remove any previous versions to make sure the override is gone: gmnumeric_2_0_0.zip Another version with a new feature - Order reference may be set to euqal cart ID (may be handy in some cases): gmnumeric_2_1_0.zip

MigrationPro. One of the best.

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.

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 ....

Merci Grok/ChatGPT^^

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

I started with PrestaShop, then switched to a different package and later switched back to PrestaShop 1.7. I'm now running PS 1.7.8.11. I tried updating to 8.2.1, but it failed. Updating to 9.0.0 wasn't possible directly. I then created a subdomain to install PS 9.0.0. I then analyzed both databases to transfer the data myself. I've now written SQL code to transfer my data. I chose to use the Hummigbird template. I think it looks very nice. And now that I've transferred my images and adjusted the colors, I think my website looks much better. But as others have mentioned, there are still some teething problems. It's a shame I couldn't upgrade from 1.7 to 9 all at once.

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.

Al parecer como siempre.. a nivel técnico no esta del todo claro las especificaciones técnicas, por eso no se ven módulos. Al final sólo los sistemas SAAS en la nube tipo holded tendrán músculo suficiente para adaptarse al infierno fiscal de este país y será mejor olvidarse de la facturación de prestashop.. Veremos

Thirtybees está desactualizado, con una comunidad pequeña y desarrollo muy lento. No es comparable ni en solidez, ni en ecosistema, ni en soporte empresarial a PrestaShop 9 ni a Adobe Commerce (Magento). Solo es una opción válida para proyectos pequeños que quieran mantener compatibilidad con módulos antiguos de PrestaShop 1.6.

It seems you haven’t met a lot of devs from Poland, have you? @WitekPr there is still a need for skilled developers, both from agencies and merchants - but PrestaShop entry level has increased, and it’s way above Woo to be considered skilled developer. If you want to increase your skills and learn to be a better developer, learn Symfony and more modern tech stack, then PS is a good option. Thanks to a tech stack used in more recent PS versions, even if you decide to stop working with PS, you’ll still have a solid foundation to work on different PHP/Symfony projects.

New free module alert!!! Compatibility with PrestaShop 1.7.x - 9.x. Scans your shop searching for any vulnerability published on the FoP security advisories list. https://github.com/prestaalba/fop_publishedvulnerabilityscan/releases

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.

strange, in incognito mode you see it the same?

Hola, Parece ser un problema conocido. ¿Puedes revisar esta solicitud de extracción en GitHub y agregar manualmente los cambios al archivo src/Core/Context/CurrencyContextBuilder.php? --- Hello, This seems to be a known issue. Can you have a look at this pull request on GitHub and manually add the changes to the src/Core/Context/CurrencyContextBuilder.php file? Please note that this is the Spanish section of the forum.

@Ray UK are you setting UK region? one of the bugs in my screenshot point to that issue. hope it helps.

1. Built-in “Our Stores” page (free) PrestaShop core has a simple Stores feature under Shop Parameters → Contact → Stores. You can add all your reseller addresses here and enable the “Our stores” front-office block. To group by country, override the StoreDetailsController and tweak the .tpl to sort your stores array by country_name and output sections per country. 2. Store Locator & Pickup with Google Maps (FME Modules) A full-featured addon that lets you: Import/export reseller data via CSV Display markers on Google Maps, auto-detecting user location Filter by custom categories (e.g., country or region) Offer a store-pickup/POS option if needed 3. Prestashop Product Store Locator (PrestaShoppe) Designed for per-product stock visibility at reseller outlets. Merchants can: Assign products to specific reseller locations Let customers search by product or address Render a clean map widget with country/group filters 4. Prestashop Store Locator (Webkul) Similar to FME’s module, with extra goodies: Marker clustering for dense areas Detailed contact info (phone, email, hours) per reseller Scheduling for store pickup slots Multi-shop and multi-language support webkul.com Recommendation: No-code / polished look: go with FME or Webkul (both include geo-API handling, CSV import, category filters). Budget-friendly / custom: use PrestaShop’s built-in Stores page or the free blockstorelocator and add your own grouping logic in the template.

Hi. Availability parameter is not available in PaymentModule.php (Not tested!!!) updated (added in green box): $productAvailableQuantity = StockAvailable::getQuantityAvailableByProduct( (int) $product['id_product'], (int) $product['id_product_attribute'], (int) $order->id_shop ); $productInfo = new Product((int) $product['id_product'], false, $order->id_lang); $productAvailableNow = $productInfo->available_now; $productAvailableLater = $productInfo->available_later; $returnAvailabilityText = ''; if ($productAvailableQuantity > 0) { if ($productAvailableNow) { $returnAvailabilityText = $productAvailableNow; } else { $returnAvailabilityText = $this->trans('Available now', [], 'Emails.Subject', $order->id_lang); } } else { $availableDate = Product::getAvailableDate((int) $product['id_product'], $product['id_product_attribute']); if ($productAvailableLater) { if ($availableDate) { $returnAvailabilityText = $productAvailableLater. '('.Tools::displayDate($availableDate, null, false).')'; } else { $returnAvailabilityText = $productAvailableLater; } } else { if ($availableDate) { $returnAvailabilityText = $this->trans('Available later', [], 'Emails.Subject', $order->id_lang). '('.Tools::displayDate($availableDate, null, false).')'; } else { $returnAvailabilityText = $this->trans('Available later', [], 'Emails.Subject', $order->id_lang); } } } $product_var_tpl = [ 'id_product' => $product['id_product'], 'id_product_attribute' => $product['id_product_attribute'], 'reference' => $product['reference'], 'name' => $product['name'] . (isset($product['attributes']) ? ' - ' . $product['attributes'] : ''), 'price' => Tools::getContextLocale($this->context)->formatPrice($product_price * $product['quantity'], $this->context->currency->iso_code), 'quantity' => $product['quantity'], 'availability' => $returnAvailabilityText, 'customization' => [], ]; and in the TPL email template (order_conf_product_list.tpl): updated (added in green box): <td style="border:1px solid #D6D4D4;"> <table class="table"> <tr> <td width="5">&nbsp;</td> <td align="right"> <font size="2" face="Open-sans, sans-serif" color="#555454"> {$product['quantity']} {if isset($product['availability']) && $product['availability']} <br>{$product['availability'] nofilter} {/if} </font> </td> <td width="5">&nbsp;</td> </tr> </table> </td> You can do the same with the ps_emailalerts module 😉

#PhenixSuite 1.6.2.33 est disponible ! 😉 Première installation ? Un seul fichier suffit: https://devcustom.net/public/scripts/dl.php?f=autoloader Changelog complet ici: https://devcustom.net/public/scripts/dl.php?f=changelog #PhenixSuite le renouveau des versions #prestashop 1.6, compatible PHP8, sécurisé et + encore à découvrir ! Concernant cette dernière version:

Hi, if the official documentation announces precise compatibilities, it's not a whim of the developers or a lack of time, just that we're certain of this data. Attempting to use other versions of PrestaShop means exposing yourself to problems, since they have not been tested and may, in some cases, cause your store to crash. PrestaShop version 9 will be compatible with more recent versions of PHP, which will oblige all third-party module developers to adapt their code to be compatible, which is absolutely not the case with PrestaShop 8. So, no, PrestaShop is neither PHP 8.2 nor 8.3 compatible, and even if you don't encounter any problems using it, there's nothing to prove that others won't have problems. So stick to the rules - you're under no obligation to switch to the latest versions of PHP. And those who talk to you about security risks, ask them to hack your site on an old PHP version and wait, because I'm saving you time, they'll never manage it.

bonjour a tous j'ai le même problème depuis quelques semaines et le support colissimo ne me donne pas de solution ... MAIS !!!!!!!!!!!!!!!!!! j'ai trouvé en fouillant sur le net, un forum wordpress ça vient du mot de passe du compte colissimo === il ne faut pas de & dedans j'ai changé le mien et ça fonctionne a nouveau, les points retrait s'affiche 🤩 si ça peut aider du monde...

Super message^^ Essaye de lire et de comprendre ce que j'explique. Moi je défends une solution française (Prestashop ne l'est plus), Open source et communautaire (Où sont les gens de Presta sur ce forum?) J'ai une solution stable avec un code 3 fois plus léger et je demande à voir tes benchmarks de 50%. Les modules suivent très bien, les seules adaptations que je dois faire concernent les versions PHP car les auteurs des modules n'ont pas vraiment mis leur code à jour. Je n'ai pour l'instant pas un module qui manquent parmi les 400 boutiques installées. Perso je crois en l'avenir et en mon travail et je considère Phenix bien supérieur en fonctionnalités et sécurité que les dernières 8 ou 9. (lire les 800 lignes du changelog) Presta a choisi une voie "technique", pas franchement à l'écoute de la communauté, moi je travaille pour mes clients qui ont de réels besoins et dont leur boutique ecommerce est leur seul CA. Je n'impose à personne de basculer sur Phenix mais pour l'instant, tout ceux qui ont fait ce choix ne le regrettent pas.

When you look in your error log you will see the following error: PHP Fatal error: Uncaught ErrorException: Warning: require(C:\\xampp\\htdocs\\var\\cache\\dev\\ContainerJiLuDQW\\getSwiftmailer_EmailSender_ListenerService.php): Failed to open stream: No such file or directory in C:\\xampp\\htdocs\\var\\cache\\dev\\ContainerJiLuDQW\\appAppKernelDevDebugContainer.php:2243 The solution that Endriu mentions and that for me worked is editing the file /app/AppKernel.php Change the function getContainerClearCacheLockPath() from protected function getContainerClearCacheLockPath(): string { $class = $this->getContainerClass(); $cacheDir = $this->getCacheDir(); return sprintf('%s/%s.php.cache_clear.lock', $cacheDir, $class); } to protected function getContainerClearCacheLockPath(): string { $class = $this->getContainerClass(); $cacheDir = sys_get_temp_dir(); return sprintf('%s/%s.php.cache_clear.lock', $cacheDir, $class); }

Vous êtes passé en MySQL 8 chez OVH et votre version Prestashop n'est pas compatible. Il faut patcher la fonction Product::getAttributesResume() en ajoutant un ORDER BY $combinations = Db::getInstance()->executeS(' SELECT pa.*, product_attribute_shop.* FROM `'._DB_PREFIX_.'product_attribute` pa '.Shop::addSqlAssociation('product_attribute', 'pa').' WHERE pa.`id_product` = '.(int)$this->id.' GROUP BY pa.`id_product_attribute` ORDER BY pa.`id_product_attribute` '); ligne ajoutée: ORDER BY pa.`id_product_attribute`

Bonjour, Je ne suis pas contre l’idée du Wall of Fame, mais alors vraiment pas en gros dans le menu général d’un backoffice de ecommerce, ça n’apporte rien pour le bizness, rien pour l’usage, ça surcharge le menu et nuis à l’UX pour rien. Et en termes de crédit pour les contributeurs, un énorme placard du genre a tendance à avoir tout l’effet inverse. Par ailleurs, je ne crois pas être le seul que ça ennuis : https://github.com/PrestaShop/ps_distributionapiclient/issues/62 Ne faites pas la bêtise de désactiver le module ps_distributionapiclient, si ça désactive le Wall of Fame, ça désactive aussi les mises à jour des modules natifs de Prestashop. Faites plutôt cette requête SQL pour le masquer : UPDATE ps_tab SET enabled = 0 WHERE class_name = 'AdminPsdistributionapiclient'; Vous pourrez toujours y accéder depuis cette url : https://votre-site.tld/adminrandom/modules/ps_distributionapiclient/top-contributors?_token=votretoken/ Et pour le réactiver : UPDATE ps_tab SET enabled = 1 WHERE class_name = 'AdminPsdistributionapiclient';

Hola a todos, en digitalDot hemos trabajado en este tema porque también veíamos que hasta ahora solo había APIs intermedias de pago. Hemos desarrollado un módulo específico de VeriFactu para PrestaShop (compatible 1.7 y 8 ) que conecta directamente con los requisitos de la AEAT y automatiza la facturación cumpliendo con la normativa antifraude. Aquí explicamos en detalle cómo funciona y resolvemos las dudas más frecuentes: https://www.digitaldot.es/prestashop-verifactu-facturacion-obligatoria/ Si queréis más información o una demo, podéis escribirnos a través del formulario de contacto de digitalDot. Un saludo!

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

PD: olvídate de actualizar a PS8 con el 1 click upgrade, solo los módulos de pago como Migration Pro dan garantías de verdad, y de hecho te permiten hacerlo a una velocidad increíble. Si necesitas apoyo con esto, tengo servicio de actualización en descuento, te incluyo consultoría y tutoriales gratis si veo que necesitas algo. Ánimo!

El video es una vision general pero no realista para una pequeña tienda o una con muchas personalizaciones ¿ Pensando en migrar ? 1 - A menos que la tienda sea muy basica y no use casi modulos externos hay un costo de actualizacion mas alto que cuando se migro de la 1.6 a la 1.7. No van a poder migrar automaticamente con una tienda con muchos modulos sobre todo si son viejos. 2 - Revicen si sus modulos son compatibles con PS 9 incluso modulos que son muy utilizados del store todavia no son compatibles. Hay modulos claves como de busquedad, filtros y de forma de pago que no funcionan por ahora. (No he revisado los de despachos pero imagino que los mas personalizados tendran problemas ) 3 - Modulos personalizados necesitan revisarlos porque a menos que sean muy basicos hay cambios en algunas clases sobre todo de Symfony (por ejemplo Symfony\Component\Translation\TranslatorInterface a Symfony\Contracts\Translation\TranslatorInterface cambio facil pero no es automatico hay que revisar ) 4 - Incluso si los modulos funcionan en php 8.1 revicen que funcionen en 8.4 porque pueden tener problemas 5 - Hasta ahora no he encontrado problemas con los modulos front-end ni con el nuevo tema pero si usan una plantilla que depende de modulos propios para que funcione la probaria primero en una tienda limpia a ver si funciona. ¿Debo migrar? yo diria siempre que si * Yo recomendaria ahora solo si tu tienda es basica y no requiere modulos externos * Si tienes muchos modulos debes esperar a que se actualicen y si es personalizado revisar.

I’m not sure what you’re asking. If your server doesn’t support exec and PrestaShop uses it, as clearly shown in the error you shared, then it simply won’t work. Unless you contact your hosting provider and they change the server settings. You can clear the cache manually by deleting the contents of these folders: var/cache/dev/* var/cache/prod/* You could also rewrite the function in PrestaShop, but that doesn’t make sense in the long run.

No, there is no such option in PrestaShop. The PrestaShop default shipping works only based on the product price and weight. So you can define the Price and weight impact on the combination level, not the dimensions

UPDATE : my store was not hacked. The problem came from a shipping module (Canada Post: Rates and Estimator by ZH Media) which was missing translations. Somehow that caused the specific cache file to be rewritten on every request. It took a long time to find the cause, but once i found it, just filling the missing translations for the module fixed the problem.

Hola@jmeca Con eso se oculta pero no se soluciona. Me gusta solucionar las cosas en lugar de "esconderlas". Luego pasas a modo debug y aparece todo tipo de errores por todas partes y resulta mucho más difícil encontrar los errores importantes. Añado a quien pueda interesar. La solución a esas dos "NOTICE" son modificar un par de lineas en el archivo redsys_3ds.php linea 185: Donde dice $billAddrLine2 = $billingInfo->address22; Debe decir $billAddrLine2 = $billingInfo->address2; Linea 203: Donde dice $mobilePhone = $billingInfo->mobile_phone ? array("subscriber"=>$billingInfo->mobile_phone, "cc" => "34") : null; Debe decir: $mobilePhone = $billingInfo->phone_mobile ? array("subscriber"=>$billingInfo->phone_mobile, "cc" => "34") : null; Como se puede ver, son dos simples avisos que se ocultan al pasar a modo producción, pero la realidad es que se está perdiendo la información de la segunda linea de la dirección y el teléfono móvil. Un saludo.

Solved. Activate the PrestaShop Edition Basic module.

Hi all, I added some "test" stock manually and it appeared in the search. I then deleted the stock and imported the data from a CSV file, and nothing appeared. I then edited a couple of items and saved them, and they then showed. So it seems that imported items are not indexed until "saved", The answer to this problem lies in the back office CONFIGURE > Shop Parameters >search, then click on either of the following, depending on the size of your database and if it's just some of the stock that's not showing, Add missing products to the index Re-build the entire index I did "entire" and it took seconds, but there were less than 300 items to process. Good luck Chandigar-IT.uk

Go to Shop Parameters -> Customer Settings ->Groups Select each Group and modify to Taxes included Take a look here:

Hi, Yes, you will face this issue with cloudflare. You need to disable cookie check on the IP. To achieve the same go to Admin -> Advanced Parameters -> Administration & set Check the cookie's IP address to No. Hope it will help.