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.

It is online again. I found that the problem was a bit wider. The new version - 1.36m - should solve it.

Mare sure the iframe parameter is allowed

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.

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.

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

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

Using the strongly worded title of "Destroying Prestashop" to bring attention to a possible Prestashop spam campaign to degrade/fatigue Prestashop installers/operators. Managing 8 PS shops and 4 shops for others and the amount of email/customer spam is bringing fatigue (even brand new sites with PS installed receive spam in hours). Wanted to bring this topic up before 2026 in hopes of keeping myself/others on PS. All ideas welcome and captchas are used

Vous n'auriez pas un override de Cart.php ou Carrier.php ou CartController.php ? Des modules accrochés sur le hooks actioncartSave ? Car là les prix arrivent directement du serveur, rien n'est modifié en js, donc c'est un module ou un override qui modifie les prix (en code je dirai qu'une boucle est mal fermée ou qu'une valeur par référence n'a pas été unset())

Hola @Surática Software, finalmente completasteis la auditoría que estabais haciendo por lo que proporcionais algún tipo de "declaración responsable" para vuestro módulo? cuando hablé con vosotros estabais con ello creo... saludos

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

I just disabled PS contact us form. e-mail address is left and those who wanna can contact and somehow e-mail providers are better dealing with spam...

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

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!

Lo que ha pasado es vergonzoso.. es lo que dices tú .. damos 3 meses sin sanciones..o lo que sea.. pero ya se había avisado lo suficiente como para a falta de menos de un mes hagan esto.. no me cabe en la cabeza la panda de inútiles que nos gobierna.. Antes de ayer se dio de alta un cliente en tu servicio, otro estaba apuntado, a espera de contratar el servicio, uno con 2000 facturas mensuales. Evidentemente han dicho que hasta el año que viene nada (lógico). El perjuicio económico que os han causado es inmenso... Ánimos Saludos Enrique

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

Hello, Oh, yes, that's how it was working in PrestaShop 1.7.x too. Both the preview and the search page will add entries to that table Glad I could help

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

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

@El Patron I'm not fighting here... I'm not going to apologize cause people this time getting too easy insulted even when nobody was trying to insult them. Statement you're not reading is because @gaminn writes that search result (looking by/for product number) with his product number is given from the post in prestashop forum with domain extension .com and not showing on search results from his eshop with same extention .com (and you state, that the problem is domain extension). I run through google docs for dev about search results, maybe too fast, but found nothing about domain extension influence an search results (btw @gaminn check on these docs maybe some thoughts after that)... FYI .us=USA domain name extension relevant to country. gTLD's are not country associated so my saying that .com=US (is another bullshait is correct). I said reading helps, so put these in search and check "what is gtld by country" , "domain name extensions by country" , "domain name extensions and search results" . I did not dispute your contribution to this community helping with prestashop issues, but sometimes i have doubts about who is the real author of your answers. @El Patron the saying, that someone who has nothing to do but to change what is working properly - was not about you, but if you think so - it's not my problem. Just read, not imagine (the talk was about search engine rules and data rankings, so I don't think you are making them) ...

you should then also read the information I posted, you in same boat. The original poster thought I made up .com vs .eu and how that is major problem for him...so you should pretty easily rank higher than him if you already don't. Friday, I feel a little more freedom of speech. Seldom does anyone follow advice here, they already have some answer in their head and they will focus on that until they go out of business..

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/

Hello! Pulling my hair out on this one. We have a website where orders with a valid VAT number should remove the VAT. They should be created with the proper prices/taxes We tested several modules and can get the actual business logic to work, as long as Vies returns proper data. However, some member states have rate limits or maintenance periods, which means addresses can't be flagged as valid before order creation => created orders include taxes => the merchant has to jump through hoops to re-validate and trigger a new calculation of the order taxes/prices. The customers also receive the erroneous values. Has anyone found a satisfactory solution to this? Which module do you use? What's your process? I'll take any suggestions at this point. Thanks in advance!

I had too many problems with this module. I found one (the only one, actually) on the PrestaShop store, and it works perfectly. For me, free modules are a thing of the past; too many problems and no support in case of issues or PrestaShop updates. Module : https://addons.prestashop.com/en/invoicing-accounting/96104-hs-codes-international-customs-nomenclature.html

UPDATES VERSIONS Version 1.3.0 (Major) Major Features: Saved layouts system: users can save, load, and manage custom layouts Add a Copy Paste in right click menu (copy block, copy styles, paste block, paste styles) Version 1.2.2 (Minor) Bug Fixes: Fixed wrapper detector allowing 'body' to be used as a valid wrapper.

Stripe paypal then it depends on what country you sell in and providing payment options they are comfortable with, klarna etc.

When you download something from Github it automatically renames it to the branch you download it from, and in this case that is the "main" branch. But to answer your question, yes the version from Github and the first post of this topic are still the latest. I would advice you to simply download the the zip file from the first post.

Hey everyone 👋 I’m sharing a small module I built for PrestaShop: 👉 PromoBar, a fully configurable announcement banner to display messages, promotions, or important updates at the top of your store. 🎯 Main Features ✅ Multilingual message with mini-formatting (bold, link) ✅ Configurable display dates (start and end) ✅ Automatic countdown if an end date is set ✅ Customizable action button (text, URL, and colors) ✅ Light animations (marquee, pulse, blink, or none) ✅ “Close” button with cookie duration (1 to 365 days) ✅ Full customization: background color, text color, local fonts ✅ Respects user accessibility preferences (reduced motion) ✅ Compatible with multi-store and Creative Elements (Elementor for PrestaShop) ✅ Tested on PrestaShop 1.7 → 9.x, PHP 7.4 → 8.3 🧠 About the module PromoBar is designed for merchants who want a clean, simple, and efficient banner — no external dependencies. The goal: inform without disturbing, and manage everything easily from the back office in just a few clicks. 🚀 Useful Links 🔹 Download for free: https://bedom.fr/boutique/extensions-plugins/promobar 🔹 Live demo: https://www.bedom.fr/demo/ 🔹 Author: BeDOM – Web Solutions 🧩 Compatibility PrestaShop 1.7.x → 9.x Creative Elements (Elementor for PrestaShop) PHP 7.4 → 8.4 Modern themes (native hooks, non-intrusive structure) ⚖️ License PromoBar is distributed under the MIT License. You’re free to use, modify, and adapt it as long as the original author credit (BeDOM – Web Solutions) is preserved. 📄 License details available on GitHub: 👉 https://github.com/bdomat/promobar 💬 Feedback welcome This is the first version (v1.0.0). Feel free to share your feedback, ideas, or improvements — I’ll keep refining it based on community input. 🧑‍💻 Author: BeDOM – Web Solutions 📍 Web development – PrestaShop & WordPress 🌐 https://bedom.fr 💡 If you find it useful, a quick “thank you” or a small feedback means a lot 😄 promobar.zip

Bonjour, peut être essayez de regarder du coté de vos directives PHP, changez les valeurs pour : memory_limit = 512M max_execution_time = 300 upload_max_filesize = 64M post_max_size = 64M max_input_vars = 5000 ça devrait aider entre autres à faire passer les longs scripts d'installation...

Have you did the htaccess reset? Disable friendly url's, save and enable it again.

there is an open issue on github here you can vote it up and if you create login add your own comments. I assume the code update you made solved your issue....but seems correct to me

Acabamos de lanzar en OleaIT un buscador inteligente para PrestaShop y WooCommerce que está funcionando muy bien. 🔎 Olisearch Es rápido, relevante, se integra en 1 hora… Y lo mejor: es gratuito hasta 1.000 búsquedas al mes. Sin permanencias ni líos. Tras las 1.000 búsquedas se desactiva o puedes pasar al plan básico por 25€ que ofrece 10.000 búsquedas. Solo necesitas instalar el módulo, y nosotros nos encargamos del resto. Además, tendrás acceso a estadísticas y soporte prioritario. 🖥 Web: https://olisearch.com/ 🎥 Vídeo (1 min): https://www.youtube.com/watch?v=CZ7NH7q6kSM Interesados por privado 😉

Please share which PS versions it's compatible with. I am doing a 9.0.1 and client wants hummingbird so I don't have a lot of front office flexibility, this could do the trick!

Pour ceux qui cherchent à revenir sur la formule Offre Unique de base appelée "Offre Unique Grow": Compte O2S > Gérer mes Services > Sur la ligne "Offre Unique Cloud", allez complètement à droite sur les 3 petits points et sélectionnez "réajuster l'offre" et là vous pourrez reprendre l'ancienne formule "Offre Unique Grow". A savoir qu'à partir de l'année prochaine le nom de domaine ne sera plus inclut dans la formule "Offre Unique Grow". Donc 1.00€ en moyenne en plus par mois. Si vous gardez l'offre qu'ils vous proposent "Offre Unique Cloud": Vous pouvez si vous le désirez prendre l'offre sur 3 ans en cliquant 2 fois sur le flèche à droite de la proposition de renouvellement. Ce qui revient à 9.00€ht au lieu de 16.00€ht mensuel, soit 324.00€ht (252.00€ d'économie, pour faire passer la pilule) Vous y gagnez un support technique Niveau 2 Prioritaire 24/24 7/7 et le TigerGuard. Par contre il faudra sortir 388.80€TTC d'un coup, ou si j'ai bien vu, paiement en 3 fois sans frais. La machine de la formule "Offre Unique Cloud" est plus puissant mais la plupart des sites de vitrine ou site E-commerce de bases n'en ont pas besoin. Après une demande d'analyse au près de O2S des ressources utilisées, un des site e-commerce mis en place avec 30 à 50 commandes par jours peut rester sans soucis sur la formule "Offre Unique Grow". Il est vrai que mettre tout le monde sur l'offre à 16€, sans analyse d'O2S des ressources utilisées par le compte, est un peu radical. Mais c'est à vous de voir.

Hi lorenxo! Have you tried to contact Prestashop support team with your issue? You can do it via this link: https://addons.prestashop.com/en/contact-us?id_product=46347 If the issue remains, I kindly invite you to try the Paypal Official module which also have express checkout button. If anything, we will be glad to help you. Regards, Daria support 202-ecommerce

Hello, I just tested with PS 8.1.7 and it does work as expected. Can you add the following CSS code to admin/themes/default/css/overrides.css file: .bootstrap .page-head .page-title { color: green !important; } Then go to the dashboard page and hard reload the browser window (Ctrl + Shift + R or Ctrl + F5 in Chrome). At this point, the title of the page should be green, as shown in my screenshot below. For the new admin pages (the ones that do not follow the index.php?controller= URL pattern), you will need to create the admin/themes/new-theme/css/overrides.css file and add your custom styles there

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

Well, this post is to validate that the "New members" group has been activated. As you can see, first content of a new members will have to validated, and this is made clear to them with a red message. After some time and approved content, a rule is set to move new members into the regular "Members" group. This way of welcoming new members has been made mandatory because of the regular spam or troll attack on the forum. This way, it is very easy to identify new users that are coming here to make noise, instead of being part of the community. Please note that this is currently a common way to manage new users on many forums, Facebook groups, and other online communities. Current version of Invision forums allow to set automatic rules, please expect that they will be use to give more power to the user, to report and block bad content and bad members, for the benefit of the community 😉

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

It seems that the attachment on my previous post didn't worked... I'm pasting here the code of the script: #!/bin/sh # Prestashop product edition using webservice. # V: 1.0 # D: 7 Oct, 2011 # Author: Jorge Solla (jorgesolla (A T) gmail (D O T) com) # WARNING!!!!!!: Before using this script, you *MUST* create a config.inc file with your shop parameters containing the following vars: # WS_KEY=<YOUR PSHOP WEBSERVICE KEY> # BASEURL=http://MYSHOP.COM/prestashop/api # Get configuration params source ./config.inc if [ $# -lt 2 ] then echo "Usage: $0 <PSHOP_ID> [ACTIVE=1/0] [QUANTITY=value] [PRICE=value] [WPRICE=value] [REFERENCE=value] [DESC=\"value\" NOTE: double quotes!!] "; echo "Example: $0 1234 ACTIVE=0" echo "Example: $0 1234 STOCK=500" exit 1; fi # Evaluate all parameters PCOUNT=0 for param in $* do # Param 0 doesn't need evaluation -> Product ID in PS if [ $PCOUNT -gt 0 ] then eval $param fi # Inc param count ((PCOUNT++)) done; # Get product ID from first param ID=$1 # Retrieve current product on PRESTASHOP CURL_REPLY=$( curl -s -u "$WS_KEY:" $BASEURL/products/$ID ) if [ $? -gt 0 ] then echo "Error: Curl was unable to connect to PS webservice" exit 1 fi # Get reply length: When we request a non-existent product, prestashop returns OK but NO data LENGTH=${#CURL_REPLY} if [ $LENGTH -eq 0 ] then echo "Error: Product ID [$ID] does not exist" exit 1 fi # Search for errors on the reply RESULT=$(echo "$CURL_REPLY" | grep "error") LENGTH=${#RESULT} if [ $LENGTH -gt 0 ] then echo "PS WEBSERVICE: Error detected fetching product ID [$ID]. Unable to continue."; exit 1 fi # Prestashop requires to delete some keys from the product XML to use it as an update XML XML=$CURL_REPLY XML=$(echo "$XML" | xmlstarlet ed -d '/prestashop/product/position_in_category') XML=$(echo "$XML" | xmlstarlet ed -d '/prestashop/product/id_default_combination') XML=$(echo "$XML" | xmlstarlet ed -d '/prestashop/product/id_default_image') XML=$(echo "$XML" | xmlstarlet ed -d '/prestashop/product/manufacturer_name') echo -n "Setting new values: " # Insert new values into fields if [ -n "${ACTIVE+x}" ] then echo -n "ACTIVE=$ACTIVE | " XML=$(echo "$XML" | xmlstarlet ed -u "/prestashop/product/active" -v "$ACTIVE") fi if [ -n "${QUANTITY+x}" ] then echo -n "QUANTITY=$QUANTITY |" XML=$(echo "$XML" | xmlstarlet ed -u "/prestashop/product/quantity" -v "$QUANTITY") fi if [ -n "${PRICE+x}" ] then echo -n "PRICE=$PRICE |" XML=$(echo "$XML" | xmlstarlet ed -u "/prestashop/product/price" -v "$PRICE") fi if [ -n "${WPRICE+x}" ] then echo -n "WHOLESALE_PRICE=$WPRICE |" XML=$(echo "$XML" | xmlstarlet ed -u "/prestashop/product/wholesale_price" -v "$WPRICE") fi # Create a tmp file to update the article (Create a PUT file for CURL) ARTICLE_DATA_FILE=$(mktemp) echo -e "$XML" > $ARTICLE_DATA_FILE # Update product CURL_REPLY=$( curl -s -u "$WS_KEY:" -i -H "Content-Type:application/x-www-form-urlencoded" -X PUT -T "$ARTICLE_DATA_FILE" $BASEURL/products/$ID ) # Check CURL return status if [ $? -gt 0 ] then echo "Error: Curl was unable to PUT the modified product" # Delete TMP file before quitting rm $ARTICLE_DATA_FILE exit 1 fi # Delete TMP file rm $ARTICLE_DATA_FILE # Search for errors on the reply RESULT=$(echo "$CURL_REPLY" | grep "error") LENGTH=${#RESULT} if [ $LENGTH -eq 0 ] then echo " -> OK"; exit 0 else echo "" echo "Error: PS Returns error while updating ID [$ID]"; echo "$CURL_REPLY" exit 1 fi

http://www.presta-addons.com/moduly/3-pdf-rozsireni.html Možnosti úprav nekonečné. Můžeš si s podobou katalogu hrát hodiny a dny. Navíc modul umožňuje tvořit vlastní faktury, které se nemusí s každou novou verzí Presty předělávat.