Leaderboard

Opracowałem sobie prosty moduł, dodający do sklepu możliwość wyboru paczkomatu zgodnie ze specyfikacją Geowidget v4. Moduł po instalacji tworzy nowego przewoźnika, którego trzeba skonfigurować i aktywować (uwaga! nie kasować go bo będzie trzeba przeinstalować moduł). Następnie w procesie zamówienia przy tym przewoźniku pojawia się możliwość wyboru paczkomatu, który potem jest widoczny na karcie zamówienia w sekcji Wysyłka. Moduł na sklepie demo Zapraszam do testowania i zgłaszania uwag! Moduł dla wersji minimum 1.7. Aby pobrać moduł trzeba być zalogowanym na forum, najlepiej pobrać zawsze wersję najnowszą. gmparcellocker_1_0_0.zip Aktualizacja - wersja 1.1.0 Dwie nowe funkcje: dostępna zmienna {gmparcellocker}, którą można wykorzystać w szablonach maili order_conf i new_order opcja zamiany adresu dostawy na adres paczkomatu - uwaga! aby ta zamiana była widoczna wszędzie, najlepiej żeby moduł był pierwszy podpięty na hooku actionValidateOrder gmparcellocker_1_1_0.zip Aktualizacja - wersja 1.2.0 Integracja z Baselinkerem - aby dane paczkomatu pokazywały się jako punkt odbioru. Przy integracji przez API po instalacji modułu trzeba w ustawieniach klucza API zaznaczyć wszystkie uprawnienia dla zasobu bl_order. Powinna działać również integracja przez plik (z informacji od użytkowników Baselinker uwzględnia moduł przy tym sposobie integracji) gmparcellocker_1_2_0.zip Aktualizacja - wersja 1.2.1 Lekko zmieniony sposób wyświetlania przycisku uruchamiającego mapę, aby umożliwić współpracę modułu z modułem One Page Checkout. Aby to działało konieczne może być włączenie opcji "Włącz kompatybilność z modułami wysyłkowymi" w module OPC. gmparcellocker_1_2_1.zip Aktualizacja - wersja 1.2.2 Dodana poprawka wprowadzona przez autorów modułu SuperCheckout + parę zmian kosmetycznych w kodzie. gmparcellocker_1_2_2.zip Aktualizacja - wersja 1.3.0 Nowa funkcja - możliwość ustawienia sposobu wyświetlania wyboru paczkomatu - okno modal lub lista rozwijana gmparcellocker_1_3_0.zip Aktualizacja - wersja 1.3.1 Dodane zmiany wprowadzone przez autorów jeszcze kolejnego modułu OPC, zmiana w tłumaczeniach na "Paczkomaty 24/7" gmparcellocker_1_3_1.zip Aktualizacja - wersja 1.4.0 Możliwość wyświetlenia informacji o wybranym paczkomacie w dowolnym miejscu w szablonie. Robimy to za pomocą widgetu: {widget name='gmparcellocker'} gmparcellocker_1_4_0.zip Aktualizacja - wersja 1.4.1 Dodane tworzenie drugiego przewoźnika - "Paczkomaty 24/7 w weekend", przewoźnik działa na takiej samej zasadzie jak podstawowy, tylko dla wyboru paczkomatu na mapie (nie jako lista rozwijana) gmparcellocker_1_4_1.zip Aktualizacja - wersja 1.4.3 Drobne poprawki na podstawie dyskusji tu na forum gmparcellocker_1_4_3.zip Aktualizacja - wersja 1.4.4 Unikanie konfliktu z modułem Baselinker, kasowanie danych z bazy w sytuacji gdy klient się rozmyśli i wybierze dla zamówienia innego kuriera. gmparcellocker_1_4_4.zip Aktualizacja - wersja 1.4.5 Tworzenie nowego przewoźnika "Paczkomaty 24/7 pobranie". Nie różni się niczym innym od zwykłego i weekendowego poza nazwą. Zrobione jest to przy założeniu, że każdy paczkomat może być pobraniowy. gmparcellocker_1_4_5.zip Aktualizacja - wersja 1.4.6 Drobne poprawki związane z przekazywaniem zamówień do BL. gmparcellocker_1_4_6.zip

within your class classes/Validate.php - either in the native code, or into an override, add this function public static function isCustomerName($name) { if (preg_match(Tools::cleanNonUnicodeSupport('/www|http/ui'),$name)) return false; return preg_match(Tools::cleanNonUnicodeSupport('/^[^0-9!\[\]<>,;?=+()@#"°{}_$%:\/\\\*\^]*$/u'), $name); } Then modify inside classes/Customer.php 'lastname' => array('type' => self::TYPE_STRING, 'validate' => 'isName', 'required' => true, 'size' => 32), 'firstname' => array('type' => self::TYPE_STRING, 'validate' => 'isName', 'required' => true, 'size' => 32), by 'lastname' => array('type' => self::TYPE_STRING, 'validate' => 'isCustomerName', 'required' => true, 'size' => 32), 'firstname' => array('type' => self::TYPE_STRING, 'validate' => 'isCustomerName', 'required' => true, 'size' => 32), A script to automate the fix https://area51.enter-solutions.com/snippets/122 For 1.3 and 1.4 the code is here:

With this module you can replace the old prestashop breadcrumb with the new Schema structure required by Google. Of course if your breadcrumb markup is modified in your theme, you'll also need to adjust the markup of this module in it's tpl file. But usually those are simple changes. To implement this module you need to remove the old breadcrumb div and insert a new hook in your theme's breadcrumb.tpl file (details are displayed after installing the module). gmbreadcrumb_1_0_2.zip Update with a new option allowing you to decide if the last item should be a link: gmbreadcrumb_1_1_0.zip If you want the last item to be linked, you execute the hook like this: {hook h='displayModernBreadCrumb' path=$path linkLast=true} If you don't want the last item to be linked, you execute the hook like this: {hook h='displayModernBreadCrumb' path=$path} (according to Google's specs the last item is not required to be a link) Another update with bug fixes gmbreadcrumb_1_1_1.zip Another update, module not needed, just replace the breadcrumb.tpl file: breadcrumb.tpl

Concernant le dernier hack #prestashop en cours, voici un script de contrôle et de nettoyage (Ouvrez le zip, prenez le fichier cleaner.php et placez-le à la racine de votre site, puis appelez-le avec cette url: https://votresite.com/cleaner.php) Ce script a été écrit principalement pour cibler le hack en cours mais il contrôle également l'intégrité générale de votre boutique. Il est fortement conseillé de l'appeler régulièrement pour vérifier que tout est ok. Le script se met à jour automatiquement à chaque appel si une nouvelle version est disponible. Il est conseillé de passer votre boutique en maintenance ou mode catalogue si elle est infectée. Une fois les nettoyages terminé et les fichiers restaurés et que toutes les lignes principales sont en vert vous pourrez réactiver votre boutique. - Script compatible toutes versions Presta - Support PHP de 5.6 à 8 - Aucun fichier cœur n'est supprimé. Ils sont éventuellement corrigés pour bloquer les infections mais je vous conseille de restaurer les fichiers d'origine (fournis avec le résultat du script) - Un rapport complet vous est fourni. Exemple sur une boutique bien infectée : Pour rappel, si vous avez des lignes en rouge, corrigez les fichiers au plus vite et modifiez vos mots de passe employés en BO car il y a de fortes chances que ceux-ci aient été récupérés. cleaner.zip Autre lien si celui ci-dessus ne fonctionne pas: https://shop.devcustom.net/fr/content/16-nettoyage-hack Pour rappel, cleaner est intégré dans les versions PhenixSuite : https://eoliashop.com/prestashop-new

Hi, This is for all who likes to add google analytics on their shop. If you are directly configuring 'Google analytics' by the module don't do it because it'll not work properly. You will get all the insights at first and after some time it'll stop giving insights at all. (Personal experience) So What I did is add this code in my header.tpl file in template/_partials but don't forget to add {literal}{/literal} at the starting and closing of the tag else you'll get a blank white page. {literal} <!-- Global site tag (gtag.js) - Google Analytics --> <script async src="https://www.googletagmanager.com/gtag/js?id=UA-134165817-1"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-*********-*'); </script> {/literal} Hope it helps

Same problem after upgrade my site , so I'm trying to change the function UpdateCart in the file (/themes/core.js) : before : o.default.cart = e.resp.cart; after o.default.cart = e.reason.cart; it works in my case

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

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

fyi if you have this issues. try this (to regenerate the .htaccess file) PS.16 preferences-->seo & urls-->scroll down-->disable friendly url, if already disableD then enable---->click save now return friendly url to enabled/disabled that you were using-->click save PS.17 Shop Parms-->seo & urls-->scroll down-->disable friendly url, if already disableD then enable---->click save now return friendly url to enabled/disabled that you were using-->click save go to website and hit F5

Hi Mustang80, We are also on PS 1.7.2.4 and had the same problem. With help of tips at https://www.prestashop.com/forums/topic/597944-search-two-or-more-words/?tab=comments#comment-2631092we modified the file classes/seach.php. This solved the problem in our site. Seach is getting exact results now.Attached the modified search.php file. Rename the file to search.php and upload to your server.Best regards,Peter PS-1.7.2-modified-for-or_Search.php

Depuis le 03-MAI-2019, la version 1.6.1.24 intègre ce patch. Si rien ne vous en empêche, Mettez à jour. Si vous continuez car vous ne pouvez pas mettre à jour. Assurez vous d'utiliser un éditeur de source respectueux de l'encodage de caractère. La méthode la plus simple (1.5.4.1+ à 1.7): Un script qui fait ça tout seul https://area51.enter-solutions.com/snippets/122 (1.5.4.1+ à 1.7) Créez une fichier patch122.php dans votre répertoire admin. Copier le contenu ci-dessus dedans. Lancez le patch. https://votre-domaine.tld/votre-bo/patch122.php Pour ceux qui veulent tout faire eux-même Dans votre classes classes/Validate.php - soit dans le code original, soit dans une override, ajoutez cette fonction public static function isCustomerName($name) { if (preg_match(Tools::cleanNonUnicodeSupport('/www|http/ui'),$name)) { return false; } return preg_match(Tools::cleanNonUnicodeSupport('/^[^0-9!\[\]<>,;?=+()@#"°{}_$%:\/\\\*\^]*$/u'), $name); } Modifiez ensuite dans classes/Customer.php 'lastname' => array('type' => self::TYPE_STRING, 'validate' => 'isName', 'required' => true, 'size' => 32), 'firstname' => array('type' => self::TYPE_STRING, 'validate' => 'isName', 'required' => true, 'size' => 32), par 'lastname' => array('type' => self::TYPE_STRING, 'validate' => 'isCustomerName', 'required' => true, 'size' => 32), 'firstname' => array('type' => self::TYPE_STRING, 'validate' => 'isCustomerName', 'required' => true, 'size' => 32), Pour les 1.3 et 1.4 c'est ici: Après avoir patché, Supprimez intégrale le compte client - permettez qu'il se réinscrive EDIT: Je ne suis plus ce topic. Pour toute demande d'aide le concernant, merci d'utiliser un ticket support.

As a developer, since the 1.7 version was launched, I often found myself in the need of a list with Prestashop 1.7 Smarty Global Variables and I know many others were in this situation. Same as you maybe, reading this article, you may also looking for a similar list. So here it is, use it wisely ("with great power comes great responsibility"). The most used arrays: {$urls|@var_dump} -> Contains Prestashop urls; {$shop|@var_dump} -> Contains shop variables (shop name, email, phone, etc...); {$page|@var_dump} -> Contains current page variables; {$currency|@var_dump} -> Currency variables; {$language|@var_dump} -> Language variables; {$customer|@var_dump} -> Customer variables; {$configuration|@var_dump} -> Configuration variables; {$link|@var_dump} -> Link variables; {$breadcrumb|@var_dump} -> Breadcrumb variables; And here are some ready-tu-use variables: {$currency.name} -> Name of the active currency. {$currency.iso_code} -> ISO language code enabled. {$currency.sign} -> Symbol of the active currency {$currency.iso_code_num} -> Active Currency ISO Code {$shop.name} -> Store name in Prestashop 1.7 {$shop.email} -> Store Email in Prestashop 1.7 {$shop.logo} -> Image routing store logo in Prestashop 1.7 {$shop.favicon} -> Route favicon image of the store in Prestashop 1.7 {$shop.address.address1} -> Store address 1 in Prestashop 1.7 {$shop.address.address2} -> Store address 2 in Prestashop 1.7 {$shop.address.postcode} -> Store Zip Code in Prestashop 1.7 {$shop.address.city} -> Store City in Prestashop 1.7 {$shop.address.state} -> Province of the store in Prestashop 1.7 {$shop..address.country} -> Shop Country in Prestashop 1.7 {$shop.phone} -> Store phone in Prestashop 1.7 {$shop.fax} -> Store Fax in Prestashop 1.7 {$language.name} -> Language name enabled {$language.iso_code} -> ISO language code enabled {$language.language_code} -> Language code enabled (for Spanish, fr for French, tc ..) {$language.is_rtl} -> (1 -> On / 0 Off (for when language is written from right to left) {$language.format_lite} and {$ language.format_full} -> Simulated date format and full date format {$language.id} -> Language ID enabled {$customer.lastname} -> Customer Last Name in Prestashop 1.7 {$customer.firstname} -> Client Name Prestashop 1.7 {$customer.email} -> Prestashop Customer Email 1.7 {$customer.birthday} -> Prestashop client birthday 1.7 {$customer.newsletter} -> Subscribed to the newsletter in Prestashop 1.7 (1 subscribed / 0 unsubscribed) {$customer.newsletter_date_add} -> Newsletter subscription date {$customer.ip_registration_newsletter} -> IP Registration Customers newsletter {$customer.optin} -> Subscribed to offers from our partners in Prestashop 1.7 {$customer.date_add} -> Client creation date in Prestashop 1.7 {$customer.date_upd} -> Last updated client update in Prestashop 1.7 {$customer.id} -> Customer ID in Prestashop 1.7 {$customer.id_default_group} -> Default group to which the client is associated in Prestashop 1.7 {$customer.is_logged} -> Check if the client is "logged in" in Prestashop 1.7 {$customer.gender.name [$ customer.gender.id]} -> Client Gender (Mr / Ms) {$customer.addresses [Address ID] .city} -> Client city of address 'X' that has partner. (Address ID, because a client can theoretically have multiple addresses) {$customer.addresses [Address ID] .alias} -> Address alias {$customer.addresses [Address ID] .firstname} -> Addressholder last name {$customer.addresses [Address ID] .lastname} -> Name of address holder {$customer.addresses [Address ID] .company} -> Company name of address holder {$customer.addresses [Address ID] .address1} -> Address 1 {$customer.addresses [Address ID] .address2} -> Address 2 {$customer.addresses [Address ID] .postcode} -> Mailing address {$customer.addresses [Address ID] .id_state} -> Address Province ID {$customer.addresses [Address ID] .state} -> Province address {$customer.addresses [Address ID] .state_iso} -> ISO address province code {$customer.addresses [Address ID] .id_country} -> Country address ID {$customer.addresses [Address ID] .country} -> Country of address {$customer.addresses [Address ID] .country_iso} -> ISO country address code {$customer.addresses [Address ID] .phone} -> Address phone {$customer.addresses [Address ID] .phone_mobile} -> Mobile phone address {$customer.addresses [iD Address] .dni} -> Address ID {$customer.addresses [Address ID] .vat_number} -> Customer VAT number {$customer.addresses [Address ID] .formatted} -> Client formatted address {$urls.base_url} -> Store address {$urls.current_url} -> Current address (url) where we are {$urls.shop_domain_url} -> Store domain {$urls.img_ps_url} -> Image root directory url {$urls.img_cat_url} -> Url directory of images of the categories {$urls.img_lang_url} -> Url of the language images directory {$urls.img_prod_url} -> Url of the product images directory {$urls.img_manu_url} -> Url directory of manufacturers images {$urls.img_sup_url} -> Url of the providers directory {$urls.img_ship_url} -> Url directory of images of carriers {$urls.img_store_url} -> Store url {$urls.img_url} -> Url of the image directory of the template {$urls.css_url} -> Template URL directory url {$urls.js_url} -> Template JS directory url {$urls.pic_url} -> Url file directory uploaded {$urls.pages.address} -> Url from the "My Address" section {$urls.pages.addresses} -> Url from the "My addresses" section {$urls.pages.authentication} -> Url section of the authentication page {$urls.pages.cart} -> Cart section url (order summary) {$urls.pages.category} -> Url section of categories {$urls.pages.cms} -> Url of the content section {$urls.pages.contact} - > Url section of the contact form {$urls.pages.discount} -> Url of the discount voucher section {$urls.pages.guest_tracking} -> Tracking url for unregistered clients {$urls.pages.history} -> Url from the order history section {$urls.pages.identity} -> Url of the section "Personal data" {$urls.pages.index} -> Page url {$urls.pages.my_account} -> Url section of my account {$urls.pages.order_confirmation} -> Url section of the order confirmation page. {$urls.pages.order_follow} - > Url in the "Order Tracking" {$urls.pages.order} -> Url of the order page {$urls.pages.order_return} -> Url of the order return page {$urls.pages.order_slip} -> Url of the order slip page {$urls.pages.pagenotfound} -> Url of section "404 (Page not found)" {$urls.pages.password} -> Url of the section "Recover Password" {$urls.pages.pdf_invoice} -> Pdf invoice page url {$urls.pages.pdf_order_return} -> Pdf order return page url {$urls.pages.pdf_order_slip} -> Pdf order slip url page {$urls.pages.prices_drop} -> Url section we lowered prices / products discount / discounts {$urls.pages.product} -> Product tab url {$urls.pages.search} -> Url of the searcher section {$urls.pages.sitemap} -> Site Map section url {$urls.pages.stores} -> Url of the section "Shops / Our stores" {$urls.pages.supplier} -> Url from the providers section {$urls.pages.register} -> Url log page {$urls.pages.order_login} -> Order login page url {$urls.theme_assets} -> Url of the "assets" directory of the template / themes / template / assets / {$urls.actions.logout} -> Url to close section in the store

Customers > Addresses > Set required fields for this section > Phone_mobile Make sure youre added in locations > countries > phone_mobile

Prestools is a suite of user-friendly and powerful tools to mass edit your products, orders and categories. It is a kind of Swiss Army knife that runs outside your backoffice. You can download it here and find a manual here. There are also an instruction video and a demo website. As an extra the following plugins can be bought: Features, Tags Plugin, Special Prices, Carriers, Suppliers, Combinations Copy and Delete, Image Cleanup, Multishop, Images, Customizations and Translation. Prestools was started in 2012 by putting together a small selection of tools for Prestashop. It has since grown steadily to become a comprehensive set of tools for maintaining Prestashop and Thirty Bees. It is one of the most popular downloads on the Prestashop forum. Prestools does not support stock movement registration and PS 1.6 warehousing. So if your shop uses those features you should not use Prestools for any operation in which product quantities are changed. Prestools operates outside the backoffice what allows it to be very fast. It supports multiple user accounts and logging. The main parts are: product-edit: great options for mass editing more than 50 product fields. Add categories, change prices, update descriptions - for hundreds of products at once. product csv: a flexible tool to generate csv files. product-sort: an easy way to sort products inside a category. From position 500 to 1 in a blink. With the visual sort option you can see immediately how things will look. prodcombi: edit and oversee properties of combinations of a number of products at once. order-edit: adding and deleting products and changing prices without problems. order-search: make a selection on carrier, payment type, status, etc. or just search. With csv export option. category-edit: useful for editing metadata and descriptions for SEO combi-edit: assign pictures to your combinations quickly combi-copy and combi-delete: copy, modify and delete attribute combinations using one product as a template attribute-list and feature-list: see how many products use each feature and attribute and get a product list. regenerate images for selections of products cleanup images: save on disk space by cleaning up images of deleted products shop rescue: turn off overrides and non-Prestashop modules when due to some bug you can no longer login in the backoffce. override-list and module-list: get lists of modules and of overrides and the modules might own them. eu-tax: get a quick overview how much you sold in each of the EU countries and how much VAT you withheld in the process integrity checks: find and fix database and file corruption. Installation: Unzip the downloaded file and copy the resulting files to a subdirectory below your admin directory (do not install as a PS module!).You can access the program in the browser like "www.myshop.com/myadmin/mydir/login1.php". You will be welcomed by a login screen: the default username is "[email protected]" and the default password is "opensecret". Please adapt your security settings in the "settings1.php" file. There is a mini-module included for integration into the backoffice. There is a demo-installation available. Username and password are the default. Below you find a view of the product-edit page where the description field has been made editable: Prestools is compatible with Prestashop 1.5, 1.6, 1.7 and 8 and Thirty Bees. There are a few parts in product-edit that you need to buy at the Prestools website. However, over 95% of the script is free. Among the files you will find a file prestoolssuite-module.zip. You can install this file as a module. It adds a link to your Prestools installation in the Catalog menu of the backoffice. If you find a problem, please update Prestools to its latest version before you report it here. When reporting, please mention your Prestashop version. Follow the installation instructions! This is not a module!

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

Salve e buongiorno a tutti . Dopo aver sviluppato e messo a disposizione della community questo modulo per la versione 1.6 (disponibile a questo post) il nostro reparto tecnico ha trovato un ritaglio di tempo per poterne sviluppare una versione adatta al nuovo PrestaShop, la 1.7 per l'appunto Abbiamo deciso di creare un nuovo post perché questo modulo è totalmente (o quasi) diverso da quello per la 1.6, che di fatto non funzionerebbe. Quindi riscritto appositamente per la 1.7, e compatibile con il nuovo template 'classic' (ovviamente ) Il modulo è stato creato sulla versione 1.7.0.4 di PrestaShop. Testato fino alla 1.7.7.0. Il modulo oltre ad aggiungere uno stato d'ordine specifico per il metodo di pagamento scelto aggiunge anche i template delle email con le specifiche informazioni della PostePay da dover ricaricare, quindi il titolare, il numero di PostePay e il codice fiscale del titolare. Potete personalizzare i testi delle email nel seguente percorso (dopo aver installato il modulo) prestashop/mails/it/tanzopostepay.html Accettiamo qualsiasi suggerimento per delle eventuali migliorie o modifiche da applicare. Il modulo è risk-free, ma consigliamo sempre di provarlo prima in un ambiente di test, mi raccomando. Buon download, e se vi è stato utile un like è sempre gradito v1.0.6-ps_tanzopostepay-ps17.zip Changelog Older version DISCLAIMER THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE SOFTWARE OR FROM OTHER DEALINGS IN THE SOFTWARE. DOWNLOADING AND INSTALLING THIS PRODUCT YOU ACCEPT THE TANZO ANALYSIS PROGRAM.

Hay algunas tiendas que van conectadas a un ERP, o donde los productos se suben o se modifican a través de aplicaciones externos. En estos casos puede ocurrir que se hagan modificaciones en los productos y no se vean reflejadas inmediatamente en la portada de la tienda debido a la caché de Prestashop. Parecido puede ocurrir con algunos módulos que muestran información de fuentes externas (por ejemplo, desde Facebook, Instagram o un blog externo), que a veces pueden actualizar la información y a pesar de eso que siga apareciendo en portada de la tienda la antigua, debido a que está cacheada. Para todos esos casos se puede utilizar este módulo. Solo hay que instalarle, activarle e indicar cada cuánto tiempo se quiere que se borre la caché (por ejemplo, cada hora). Transcurrido ese periodo de tiempo, se efectuará automáticamente un borrado de la caché. También se puede elegir la activación mediante CRON, proporcionando una URL cuya llamada es posible programar en el CRON del servidor con el intervalo que se quiera para efectuar el borrado de la caché. Versión 2.1.0 disponible para Prestashop 1.6 y 1.7: ftm_cacheclear.zip

I had what appears to be the same problem. This solved it. Add this logic to the if on line 390 in src/Adapter/Product/AdminProductDataProvider.php if ($formatCldr && $product['price'] != null && $product['price_final'] != null) { $product['price'] = $localeCldr->formatPrice($product['price'], $currency->iso_code); $product['price_final'] = $localeCldr->formatPrice($product['price_final'], $currency->iso_code); }

The settings below are tested in production for 500 to 20.000 products and 3 mio attributes. For to have a flexible and better server features management and also the best speed for to work with Prestashop take a dedicated or a VPS root server. Managed servers in most of the cases don't have the possibility to make own changes needed on the server configuration. You need at least php 5.6*. Better performance you will get with php 7 and mySQL 5.7 or mariaDB 10 (read also detailed PS 1.7. versions further down !!). There is no need for accelerators, in contrary, best is the use of php-fpm + opcache + ngnix proxied. memory_limit = 512M max_execution_time = 300 max_input_time = 300 upload_max_filesize = 20M post_max_size = 20M max_input_vars = 10000 allow_url_fopen = on - with that you. can import images and other accesses externally safe_mode = off cURL - installed for you for example. Paypal and other web services work without problems. mod_rewrite = installed and activated mod_security = off at least php 5.6.x* + php-fpm + opcache with its own values (see below), better performance with php 7. mySQL 5.6 or higher (better performance with mySQL 5.7 or mariaDB) JSON = ON ctype = ON mySQL = INNODB (myIsam does not work correctly) php.ini from the server must include the date.timezone Open SSL 1.0.2 or higher (Prestashop is not recommended on Windows servers) cageFS and another FIREWALL technique installed on the server configured correctly so that the back-office is not slow by blocking external services that Prestashop uses. If in doubt, or back-office slow, please ask the provider of your accommodation if there are firewalls installed !!! PS 1.7.x in detail: PS 1.7.0 -> 1.7.3. - here you can still use php 5.6.30 (above and inclusive) without problems. For better performance use php 7.1. and mysql 5.7 or maria DB 10 be PS 1.7.4. -> 1.7.6 - requires php 7.2. and maria DB 10 or mysql 5.7. BE AWARE that with php 7.1. hashing extension will be changed, this means mcrypt extension (rijndael encryption) is removed. Although mcrypt could be installed a part with PHP 7.2, this version and later one will use bcrypt (blowfish based). So please upgrade older Prestashopversions only by using 1-click-module and also on servers with php 7.1 + installed by default. Be careful with servers configured initially with php versions 5.6x and than other php versions are installed as extra. This could make problems on your site, like: Passwords will not work anymore, data could not be changed or saved anymore, etc. -> PS 1.7.7. AND HIGHER - requires php 7.3. and maria DB 10 or mysql 5.7. Opcache optimization: opcache.revalidate_freq = 0 opcache.validate_timestamps = 0 (comment this out in your dev environment) opcache.max_accelerated_files = 7963 opcache.memory_consumption = 192 opcache.interned_strings_buffer = 16 opcache.fast_shutdown = 1 In addition, it is important to have automatic permissions to create / change / delete folders and files. Thus take care that all internal scripts and users (from inside the server) will have full access to folders and files automatically, while external accesses have read-only access, without the need to change these parameters manually. * php 5.6, php 7.0 and php 7.1 are all end of life and not maintained anymore. This means that there will be no updates and also no security updates available. The best is to take newer php-versions in combination with newer PS-versions!!! Releases php-versions

Hace unos días me contactó un cliente que empezaba a tener problemas de spam y registros diarios de usuarios "fantasmas" en su Prestashop, con datos falsos (bots). Lo primero que se me ocurrió fue buscar un módulo para integrar el recaptcha de Google en los formularios. Encontré uno gratuito, el eicaptcha, pero es para la versión v2, que obliga al usuario a tener que escribir un código o resolver un pequeño puzzle para pasar la verificación. La versión 3 en cambio, pasa desapercibida y normalmente no requiere intervención del usuario, por lo que resulta mucho menos "disuasoria" para el usuario legítimo que quiere enviar un mensaje o registrarse como cliente en la web. Por tanto, intenté localizar algo para la versión 3 del Recaptcha de Google, pero lo único que encontré fue un par de módulos comerciales, uno incluso se anunciaba como "con inteligencia artificial" y pedían 50 euros por él. Veo lógico que la gente quiera cobrar por su trabajo, pero me parece mucha cara "vender" algo con el reclamo de "inteligencia artificial", cuando esa inteligencia no la has programado tú, sino que estás usando un servicio de Google y tu módulo lo único que hace es integrarlo dentro de los formularios de Prestashop para que funcione, a un precio a mi juicio excesivo para lo que hace (modificar un par de formularios y realizar la verificación de un campo que además te da Google el resultado). De modo que le eché un vistazo a ver cómo funcionaba la integración (esta página me aclaró mucho las cosas), y me puse y en un par de horitas (o más bien 4 ó 5, porque cambié varias veces de opinión sobre los hooks a utilizar) tenía un módulo funcionando. Lo dejo aquí para quien lo necesite. Antes de usarlo, algunas consideraciones: El módulo lo he creado como he explicado, lo he probado en 2 instalaciones de Prestashop y en principio funciona sin problemas, lo adjunto aquí para quien lo quiera, pero es software gratis y "as-is", es decir, no ofrezco garantías de que vaya a funcionar en todos los casos, ni me hago responsable si no funciona como debería. En el caso de que lo instales, tú eres el responsable de comprobar que los formularios siguen funcionando de forma adecuada. Si no es así, con desactivarlo o desinstalarlo todo volverá a estar como antes. El módulo es para la versión 1.7.1 de Prestashop o superior. No funciona con versiones anteriores porque algunos de los "hooks" que utiliza creo que solo están presentes desde la versión 1.7.1. El módulo permite activar el recaptcha de forma general, y luego de forma particular en el formulario de registro, en de contacto y en el de suscripción a la newsletter, por separado. Si se activa en el formulario de registro, también se activará para el registro que se puede hacer directamente en el checkout y para la compra como invitado (esto es algo que está hecho así de forma intencionada, porque por ahí también te pueden colar registros "fantasmas"). No lo he probado en instalaciones que no usen el checkout estándar de Prestashop y lleven algún módulo de "compra en un paso", y no sé si opera correctamente con ellas o no. En principio, debido a la forma que tiene de funcionar no debería dar problemas, pero como no he hecho ninguna prueba, no puedo asegurarlo. Para que el módulo funcione necesitas, lógicamente, dos claves del recaptcha v3 de Google, la clave del sitio y la clave secreta. Esas claves las tienes que generar con tu cuenta de Google desde aquí: https://www.google.com/recaptcha/admin/create Para que funcione en el formulario de contacto debe estar actualizada la template de ese formulario para que incluya el hook del GDPR (ley de protección de datos). Las versiones recientes del módulo de contacto lo incluyen todas, pero hay temas que tienen hecho overrides de esa plantilla y no están actualizadas con ese hook. Lamentablemente, la template del módulo de contacto es el único hook que incluye, por lo que hay que utilizar ése. Cualquier problema que tengáis con él podéis ponerlo aquí e intentaremos solucionarlo. Versión 1.1 disponible: ftm_recaptchav3.zip

Upgrade/Migrate Prestashop from Prestashop 1.4.x, 1.5.x or 1.6.x to latest Prestashop 1.7 has been so easy with Prestashop Migrator - the best Prestashop Upgrade module. This module comes with both Premium version and Free version. The premium version is available at: https://prestahero.com/upgrade-data-migration/149-prestashop-better-upgrade-and-migrate-tool.html The free version is attached in the downloads below (please download the latest version) We recommend you to purchase Premium version of Prestashop Migrator to upgrade/migrate your website perfectly to Prestashop 1.7. Once you purchase premium version, we also offer you 24/7 premium support to solve any problem you meet when using the module. Free version only allows you to migrate major datas (products, product categories and customers) to your new Prestashop 1.7 website. If it's enough for you, just download the free module from updated links below. We give support for free module publicly on this forum topic. Just comment on the topic what you need to help, we'll check and give answer to you as soon as we can. Update downloads for free version: -------- Version 2.1.4 (recommended) -------- - Module improvement - Bug fix - Compatible with the latest version of PrestaShop Download: v2.1.4-free-prestashop-migrator-module-please-unzip-to-use.zip -------- Version 1.4 -------- - Module improvement - Bug fix Download: v1.4-free-presta-migrator-please-unzip-to-use.zip -------- Version 1.3 -------- - Module improvement Download: v1.3-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.2 -------- - Module improvement Download: v1.2-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.1.9 -------- - Fix bug: importing products stop at 1%; all imported products are belong to one category Download: v1.1.9-free-presta-migrator-please-unzip-to-use.zip -------- Version 1.1.8 -------- - Update back end interface - Module improvement Download: v1.1.8-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.1.7 -------- - Bug fix Download: v1.1.7-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.1.6 -------- - Module improvement Download: v1.1.6-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.1.5 -------- - Fix error occurred when export multi-language of multi-shop Download: v1.1.5-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.1.3 -------- - Module improvement - Bug fix Download: v1.1.3-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.1.2 -------- - Module improvement Download: v1.1.2-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.1.1 -------- - Module improvement Download: v1.1.1-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.0.10 -------- - Module improvement Download: v1.0.10-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.0.9 -------- - Improve performance of the module Download: v1.0.9-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.0.7 ----- - Bug fixes Download: v1.0.7-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.0.6 -------- - Improve migrating speed - Use less server resource Download: v1.0.6-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" -------- Version 1.0.5-------- Version 1.0.5 is attached to the topic (at the end of the topic) and is available on What is new on version 1.0.5? - Bug fixes (missing ps_state_lang table problem on Prestashop 1.4.11.1) - Better performance - Migrate data faster - Require lower server resource - Detailed alert for any errors (with solution) if happen during the migration - Up-to-date with Prestashop 1.7.4.1 (and even later versions when they come) Download: v1.0.5-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" ----------------------------- Github project: https://github.com/ets-soft/prestashop-migrator-free-version OVERVIEW Migrate or upgrade Prestashop 1.6 (or other versions) to 1.7 is always a challenge even for advanced Prestashop users because code and database of Prestashop has been changed completely since its release of version 1.7. Understand the difficulty to upgrade Prestashop to 1.7, we have made “Prestashop Migrator – Free version” – a perfect Prestashop module that helps you migrate your website to 1.7 easily in a few simple steps. HOW TO MIGRATE MY WEBSITE TO 1.7? It’s very simple, just download “Prestashop Migrator” then follow 3 simple steps below Step 1: Install “Prestashop connector” – a free Prestashop module provided along with the download package on the source website (your old website.) Step 2: Install a fresh Prestashop 1.7 website (target website) then install “Prestashop migrator” on the website you just installed. Step 3: Start migrating your data from the source website to target website. Wait a few minutes and enjoy your new Prestashop 1.7 website. WHAT DATA CAN I MIGRATE? You can migrate the most important data to Prestashop 1.7 (or other versions 1.4, 1.5, 1.6), details listed below Products All product data such as name, ref, description, image, combinations, features, prices, specific prices, SEO settings (meta title, meta description, meta keywords and friendly URL), product ID, product quantity, product comments (if your source site has installed Product comments module), etc. Categories Name, description, image, category ID, SEO settings (meta title, meta description, meta keywords and friendly URL), etc. Customers First name, last name, customer ID, gender, birthday, addresses, passwords, etc. FEATURES Migrate Prestashop 1.4, 1.5 or 1.6 to Prestashop 1.7 Migrate data between Prestashop websites (any versions) Downgrade Prestashop to a previous version (eg: Prestashop 1.7 to 1.6) Bulk data upload (valid XML data format required) Backup data Possibility to keep customer passwords or regenerate new passwords for customers Migrate multi-shop Migrate many Prestashop websites into 1 shop (merge shops) Migrate multi-shop to separate Prestashop websites (split shops) Migration history (view migration history, resum or restart migration anytime) Clean-up (save your disk space) WHY PRESTASHOP MIGRATOR? It’s FREE There are some other Prestasho to Prestashop migration tools out there but they’re all PAID modules, you’re required to buy the modules with a lot of money. Not everyone can afford to pay for such modules so we made this module, it’s free for you to migrate the most important data from Prestashop 1.4, 1.5 or 1.6 to Prestashop 1.7. It’s complete data migration tool With Prestashop Migrator, you can migrate your most import data (products, product combinations and features, images, SEO settings, categories, customers, addresses, customer passwords, multishop, etc.) to Prestashop 1.7 in a few clicks of your computer mouse. That’s amazing! Some other paid modules out there may also not be able to do that! Fast and secure This is the fastest Prestashop migration module ever! It uses advanced technologies to migrate data such as jQuery Ajax, multi-threads, non-stop process, etc. The migration is done with a secure access token to make sure you never lose any data to a third party while performing the migration. Process large data with minimum server resource Large data is split into small pieces of data, the module processes the data pieces one by one with a minimum requirement of your sever resource. You can migrate 10.000+ products to Prestashop 1.7 in a few minutes with a low configuration server. That’s all about “Prestashop Migrator - Free version”, just download it (in the attachment of this topic) for free and enjoy! We hope you like your new Prestashop 1.7. Migrate Prestashop to 1.7 is completely safe with Prestashop Migrator! Don't hesitate, migrate your website to 1.7 now! v1.0.5-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable" v1.0.6-free-presta-migrator-please-unzip-to-use.zip *Note: You need to login to download if it shows "Unavailable"

Depuis que je connais Prestashop, il y eu une seule mise à jour concernant un problème de sécurité et c'était sur une version 1.4. Oui Prestashop est un cms très particulier. Par son code et la stratégie actuelle. Leur gros problème ce sont les tests, ils nous disent qu'ils en font, ok mais ils les font juste sur leur boutique de test avec John Doe comme seul client, 4 robes et 10 pauvres modules installés. Leur réponse est toujours la même: "On ne peut pas tester toutes les configurations". Et c'est là que le bas blesse, perso à chaque mise à jour, je commence par faire un diff avant de cliquer sur ce bouton sans réfléchir, parce que rien que le changelog c'est minimaliste et ça ne reflète pas les réels changements effectués. Correction d'un bug ? Ok, je vais voir ce qu'ils ont fait et si le bug est vraiment résolu. Ajout d'une feature ? Alors là, attention parce que généralement ça veut dire nouveaux bugs ou pas géré suivant tous les cas de figure. Ensuite, mes boutiques de test on des bases de 2 à 8000 clients en moyenne, des tas de règles paniers et prix spécifique, des configurations multi-langues et des catalogues de + de 10 000 produits. A ça on peut ajouter entre 2 et 300 modules installés. Là je considère que les tests commencent à être représentatifs. Oui Prestashop est responsable en annonçant comme fiable une version qui ne l'est pas Oui Prestashop est responsable en ne mettant en avant que cette version 1.7 et en dissimulant bien les autres (Pour info, la dernière maj de la 1.6 (1.6.1.20) date de moins de 15 jours, alors parler d'ancienne version me fait doucement rigoler) Oui Prestashop depuis 2 ans ne mise plus que sur l'aspect RENTABLE et FINANCIER de sa solution. Exit le côté communautaire, exit la fiabilité, exit les remontées utilisateurs. ils sont les meilleurs et n'écoutent plus leurs clients. Si vous voulez leur parler, ils sont planqués là: - http://build.prestashop.com/ - https://gitter.im/PrestaShop/General - http://forge.prestashop.com/ Bien sûr, vous devez écrire en anglais, sinon passez votre chemin... Symfony, on l'avait réclamé en 2011/2012 et on nous avait répondu à l'époque que le code maison de Presta était très bien comme il était et que ce n'était pas à l'ordre du jour. Smarty fonctionne bien nativement, le problème c'est que Prestashop en a tellement trituré le code que c'est devenu n'importe quoi au niveau de la gestion du cache et que les serveurs passent plus de temps à l'effacer / ré-écrire plutôt qu'à l'utiliser. (Je ne parle même pas de l'option débile d'écrire ce cache en bdd qui plante le moindre mutu...) Suite à la pression des investisseurs et de certains devs, Prestashop a décidé de passer sous Symfony pour plusieurs raisons: - Le code devenait difficile à maintenir (Ben oui, les employés actuels sont tous là depuis peu et maîtrisent très mal les 300 000 lignes de code maison) donc en passant par un framework relativement connu ce sera plus simple. - Ils espèrent faire revenir les développeurs externes vers Prestashop (modules, thèmes et GitHub) - Prestashop donne l'impression d'être à jour et dans la course Mais là encore, on fait ça à la sauce Prestashop, c'est à dire par morceaux tenus par du scotch pour que ça pète pas trop. Passer à Symfony c'est une bonne idée, oui mais leurs modules et thèmes vendus sur Addons ne sont pas compatibles (écrits pour Smarty) et ils n'ont pas le temps ni le personnel pour les mettre à jour, donc s'ils veulent continuer à les vendre, il faut conserver Smarty en parallèle. Et voilà comment on commence les conneries... La 1.7 c'est une 1.6.0.10 à la base qui utilise 2 moteurs de templates (un inédit dans le monde du CMS quand même !) et à laquelle on a supprimé tout ce qui ne marchait pas (on verra au fur et à mesure pour les remettre ou pas, mais l'objectif actuel semble plutôt se tourner vers le remplacement de ces fonctionnalités par des modules payants) Mais plutôt de ré-écrire Prestashop pour être conforme avec Symfony, ils ont rajouté une couche de compatibilité ce qui alourdit encore plus le code et crée une véritable usine à gaz. Et j'ai lu dernièrement qu'ils allaient encore en rajouter une couche pour que nous puissions continuer à écrire le code comme pour les 1.6 (Vu qu'ils peinent à donner envie aux devs externes d'utiliser leur 1.7 bancale). Alors oui, je suis désolé pour vos mésaventures, mais je ne peux pas vous encourager à continuer avec cette version uniquement parce que le nouveau principe de templates est sympa. C'est l'arbre qui cache la forêt et c'est le jour où vous allez vouloir utiliser Prestashop dans ses fonctions avancées que vous aller commencer à galérer sévère (Taxes, prix spécifiques, déclinaisons, transporteurs, stocks avancés, etc...) La 1.7 soit-disante "stable" c'est une version hybride dont les tests sont effectués sur votre dos et sans aucune assistance, et ça, c'est juste une honte.

Bonne nouvelle pour ceux qui l'attendaient, elle est à présent dispo AVERTISSEMENT: Cette version est livrée "telle quelle". Toutes les modifications et améliorations apportées ont été testées sur une boutique propre ayant ses fichiers d'origine (Override possibles) avec le thème par défaut Bootstrap. Si vos fichiers cœurs ont été modifiés, ou que l'option "ne jamais recompiler les templates" est cochée, vous risquez d'avoir des surprises une fois la mise à jour effectuée. En aucun cas je ne serais responsable des conséquences d'une mise à jour irréfléchie. En cas de doute, effectuez un clone de votre boutique actuelle et effectuez la mise à jour, puis testez le fonctionnement de votre boutique. Cette version est le fruit de nombreuses heures de travail, d'adaptations diverses déjà effectuées et testées chez nos clients et rassemble des nouvelles fonctionnalités, des corrections de bugs existants et d'améliorations diverses. Veuillez utiliser de préférence la version du module autoupgrade fournie dans le zip. A VOS TESTS ! Changelog des principales modifications apportées: PANIER - Possibilité de bloquer (rendre non modifiable) un panier sur son contenu produits (Utile lors d'un envoi de lien de paiement avec produits ou frais de ports offerts) - Blocage également du panier lors du choix de méthode de paiement (Anti-fraude) - Les paniers bloqués peuvent être débloqués ("dupliqués") par le client pour permettre leur modification CARACTÉRISTIQUES: - Suppression et intégration des valeurs "customs" comme de nouvelles valeurs, automatiquement - Possibilité de rendre visible/invisible des caractéristiques en FO - Ajout du paramètre position pour les valeurs de caractéristiques (Utile pour classer des valeurs numériques par exemple) - Ajout du paramètre Icône pour chaque valeur (Permet d'afficher des pictos en FO) SAV - Utilisation de réponses prédéfinies paramétrables - Ajout de pièces-jointes multiples depuis le BO (A voir pour ajouter cette fonctionnalité dans les pages commandes également) - Transfert d'un thread à un autre service (Service client, transport, conseil,...) - Ajout d'un bouton de suppression ENTREPOTS - Possibilité d'utiliser les entrepôts et emplacements sans activer les stocks avancés COMMANDES - Possibilité d'ajout d'une note spécifique liée à la commande - Possibilité de créer une commande gratuite en BO (free_order) - Possibilité de supprimer l'étape transporteur pour un groupe défini (Vente sur place en magasin par exemple) - Remplacement de GoogleMap (payant) par Leaflet - Possibilité de générer des factures proforma tant que la commande n'est pas payée (Virement bancaire, traite, chèque, etc...) PDF - Visualisation par défaut dans le navigateur plutôt que téléchargement systématique - Modification du traitement d'édition en masse (Génère un zip de l'ensemble des factures individuelles plutôt qu'un affichage global) PARAMETRES - Suppression des options de cache serveur et autres réglages exotiques inutiles - Ajout du choix de priorité lorsque plusieurs règles catalogue peuvent s'appliquer - Ajout du choix de l'application de règles panier sur des produits déjà remisés - Possibilité de déplacer les produits hors-stock en fin de liste pour les listings en FO - Possibilité d'afficher ou non Marques OU/ET Fournisseurs - Suppression de la dépendance à api.prestashop pour la mise à jour des monnaies PRODUITS - Ajout de statistiques par produit en page produit (et sur dashboard avec possibilité d'export) - Editeur en ligne des légendes image (Chaque champ est modifiable en direct) - Possibilité d'éditer un prix spécifique (au lieu de devoir le supprimer et le recréer) - Mise à jour des packs lors de l'ajout de stock de produits appartenant à ces packs - Ajout du champ "Phrase d'accroche" disponible pour l'objet product en FO - Correctif de l'effacement des images mini en multi-shop - Possibilité de générer des images WEBP si votre serveur le permet PERSONNALISATIONS PRODUITS: - Ajout simplifié d'éléments (texte ou fichier) - Possibilité de suppression par élément - Ajout de l'impact sur le prix par élément de personnalisation. Nécessite un ajustement de certains fichiers de votre thème (blockcart et summary) pour un meilleur rendu - Gestion des prix spécifiques liés - Refactorisation du code existant RECHERCHE - Optimisation de l'indexation et du moteur - Ajout de la recherche par référence en 1er TRANSPORT - Suppression de l'option dangereuse de gratuité dans: Transport -> Préférences (Utiliser une règle panier permet d'être plus précis et sélectif) - Correctif dans le thème bootstrap de l'affichage du delai (non-inclus par défaut dans la boucle {foreach} dans order-carrier-advanced.tpl, order-carrier.tpl et order-carrier-opc-advanced.tpl) CLIENTS - BO: Affichage des 10 derniers paniers, produits vus et commandes maximum (Possiblité d'en charger plus en Ajax) pour éviter les chargements de page trop longs pour les comptes clients ayant un gros historique - BO: Possibilité d'envoyer des messages (prédéfinis ou non) depuis la page Client GROUPES - Possibilité d'assigner toutes les catégories à un groupe en un clic MAGASINS - Gestion des adresses de type "store" en tant que véritables adresses (utile pour l'adresse de livraison en magasin sur les factures) - Suppression de la dépendance à Google pour l'affichage des cartes (remplacé par Leaflet) - stores.tpl, stores.js et stores.css à mettre à jour dans votre thème F.O. - Chargement par défaut du plugin fancybox - Protection des formulaires avec email MODULES - Ajout de la fonction displayInformation() ADMIN - Notifications si un autre employé est loggué sur la même page en cours d'édition (désactivable) - Messagerie instantanée entre employés WEBSERVICE API - Ajout du hook handleAddWebserviceResources (Permet de gérer le webservice depuis un module et générer ses propres requêtes) Le lien pour la télécharger: --> ICI <--

Bonjour à tous, nous n'avons jamais pensé à le publier ici, mais nous développons depuis quelques temps un module de page builder gratuit et open source pour PrestaShop. CE dernier est nommé PrettyBlocks, vous trouverez toutes les informations sur notre github: https://github.com/PrestaSafe/prettyblocks Vous avez également la documentation développeur en FR: https://prettyblocks.io/ Et une démonstration en vidéo du builder: N'hésitez pas à l'essayez et nous faire vos retours. Pensez à installer les classic blocks (gratuits également) https://github.com/PrestaSafe/classicblocks PrettyBlocks est utilisalable sur tout votre site, vous pouvez en gros, duppliquer vos modules (qui sont des blocks). Pour rappel ce projet est 100% gratuit, des évolutions arrivent au fur et à mesure. N'hésitez pas à nous dire ce que vous en pensez prettyblocks (6).zip classicblocks (6).zip

Módulo de ejemplo de uso de CQRS en Prestashop que añade un nuevo filtro de Grupo de Cliente en el listado Solo compatible con versiones recientes de Prestashop 1.7.6, 1.7.7 filtercustomer.zip

After reading a lot of forum topics and GitHub Issues marked as "solved", but solved only for older versions of Prestashop and, mainly, for older versions of the Faceted Search Module, I've found a solution, that works well form me. Since all the queries have been replaced by calls to Search Adapter Objects, I've modified the file: /modules/ps_facetedsearch/src/Product/Search.php at line 147, modifying the source code from this: case 'id_attribute_group': $operationsFilter = []; foreach ($filterValues as $attributeId => $filterValue) { $this->getSearchAdapter()->addOperationsFilter( 'with_attributes_' . $attributeId, [[['id_attribute', $filterValue]]] ); } break; to this: case 'id_attribute_group': $operationsFilter = []; foreach ($filterValues as $attributeId => $filterValue) { $this->getSearchAdapter()->addOperationsFilter( 'with_attributes_' . $attributeId, [[['id_attribute', $filterValue]]] ); } //modded by Antonio to hide Out of Stock combinations $operationsFilter = []; $operationsFilter[] = [ ['quantity', [0], '>'], ]; $this->getSearchAdapter()->addOperationsFilter( self::STOCK_MANAGEMENT_FILTER, $operationsFilter ); break; and finally it works!

Ok, that is it! I was so angry that I can't find any working solution for this so I created my own and it is working. This is the code which You can place in Your file or just download the attached file and put it into main folder of Your shop and run http://yourshop.pl/remove_unused_images.php in Your browser. Things to consider if you are courious but not mandatory: Change $limit value from 19 line when testing, for example like 100, for production mode use $limit = $counted_images; if scan return 0 or there is an error just check if $scan_dir is ok by adding ddd($scan_dir); arround 11 line of code. Upload script again, test it if scan directory is properly created, if not then change $shop_root and $image_folder values from the beginning of the script, remove ddd part, reupload and run script again. It might take a long time so if You will run out of time then just run the script again. Feel free to not ask about anything because I won't support this code, I am not responsible for it and I won't help You. Likes for this post will be appreciated because there are some paid solutions, modules that are doing basically the same thing. This one is free. This will take some time to process - if You have large ammount of files it can exceed your max_execution_time limit on Your hosting. If this will happen You can try to take parts like 5000 or 10 000 and edit for ($i=1 to start with for ($i=5000 and then restart the script again and again with changing the limit <?php ####PUT THIS FILE INTO YOUR MAIN SHOP FOLDER#### // root path of the shop, almost no one needs to change something here. $shop_root = $_SERVER['DOCUMENT_ROOT']."/"; // need to have slash / at the end $image_folder = 'img/p/'; // also needs slash at the ennd $scan_dir = $shop_root.$image_folder; include_once($shop_root.'config/config.inc.php'); include $shop_root . 'config/settings.inc.php'; #---------------------------------------------# $last_id = (int)Db::getInstance()->getValue(' SELECT id_image FROM '._DB_PREFIX_.'image ORDER BY id_image DESC '); $counted_images = Db::getInstance()->executeS(' SELECT count(*) as qnt FROM '._DB_PREFIX_.'image '); $counted_images = (int)$counted_images[0]['qnt']; echo 'There was '.$last_id.' images in database but only '.$counted_images.' is used right now. Lets check how many of them are eating up our storage without no reason.<br>'; //$limit = 150; // for testing $limit = $last_id; // for production $removed_images = 0; for ($i=1; $i <= $limit; $i++) { if (!imageExistsInDB($i)){ $imageDir = str_split($i); $imageDir = implode('/', $imageDir); $path = $scan_dir.$imageDir; deleteImagesFromPath($path); } } function deleteImagesFromPath($path) { global $removed_images; $images = glob($path . '/*.{jpg,png,gif,jpeg}', GLOB_BRACE); if ($images){ foreach ($images as $file) { if (is_file($file)) { unlink($file); } } $removed_images++; echo 'Deleted images from folder ' . $path . '/' ."<br/>"; } } function imageExistsInDB($id_image){ return Db::getInstance()->getValue(' SELECT id_image FROM '._DB_PREFIX_.'image WHERE id_image = '.(int)$id_image ); } echo '--------------------------------------<br>'; if ($removed_images > 0) echo 'Hurray! We removed '.$removed_images.' product images!'; else echo 'Everything is ok with Your images. I did not removed any of them or I made it before. Good Job Presta!'; remove_unused_images.php

Ok, c'est Prestashop addons qui mouline et ne répond pas. Désactivez l'appel à addons, dans /classes/tools.php vers la ligne 3352, remplacez protected static $is_addons_up = true; Par: protected static $is_addons_up = false; Une fois cela fait, si vous aviez des alertes en rouge concernant les fichiers xml, supprimez tous les fichiers xxxxxx.xml du répertoire /config/xml/ Et supprimez le module gamification du ftp: /modules/gamification

I've checked the "incognito" mode, I've also cleaned cahe and cookies in my browser - still access denied. I've made some kind of an experiment. I've kept my dev stores filesystem on server, but I've cleared DB and restore it with the one from clean Presta. Now I can get to Order and see first example orders from John Doe... I believe this means that the issue reason is in DB. Have you got any idea where to look for it? EDIT: Problem Solved! I've restored 'my' DB, removed 'ps_access' table, and restored 'ps_access' from 'clean' DB. Now it all works fine Thank you guys for help! In attachement there is 'ps_access' table from clean DB - in the case if someone would need it in the future ps_access.sql.gz

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.

The debug mode is widely used to see the errors on your shop and when: you get blank pages; you get 500 Internal Server Error; you have strage issues with your shop and don't know where to start; Edit: Debug mode on PrestaShop 8.0 PrestaShop Dashboard > Advanced Parameters > Performance > DEBUG MODE PANEL > Set it to YES Debug mode on PrestaShop 1.7 PrestaShop Dashboard > Advanced Parameters > Performance > DEBUG MODE PANEL > Set it to YES To turn on the Debug mode on PrestaShop 1.7 is more simple comparing it to the previous versions of Prestashop. You can do this from your PrestaShop Dashboard > Advanced Parameters > Performance > DEBUG MODE PANEL > Set it to YES If you can't acces you dashboard you can also enable it through FTP by accessing config/defines.inc.php and usually @line 29 you will find: define('_PS_MODE_DEV_', false); change it to: define('_PS_MODE_DEV_', true); Turning on the Debug Mode on other versions of Prestashop Debug mode on PrestaShop 1.5.3 to 1.6 For PrestaShop 1.5.3 to 1.6 the procedure is the same: Open config/defines.inc.php and usually @line 29 you will find : define('_PS_MODE_DEV_', false); change it to: define('_PS_MODE_DEV_', true); For PrestaShop below 1.5.3 you have to edit the config/defines.inc.php file and make the following changes: Change this line: @ini_set('display_errors', 'off'); to this: @ini_set('display_errors', 'on'); !!! Be careful, turn the Debug Mode off when finished debugging, hackers may get advatage of it and may harm your website and besides of that any visible error is not good for visitors. Debug mode for Admin or specific IPs Because Debug mode should not be visible for your customers here's a smart solution that allows you to enable it only for admins or for some provided IPs. This way your shop will not be vulnerable while you debug.

Concernant le dernier hack #prestashop, un script de nettoyage (Ouvrez le zip, prenez le fichier cleaner.php et placez-le à la racine de votre site, puis vous l'appelez avec cette url: https://votresite.com/cleaner.php) https://devcustom.net/public/scripts/cleaner.zip ** Edit** Le script se met à jour automatiquement. Pour info, la description que donne prestashop n'a pas grand chose à voir avec le hack actuel^^ L'avis de @doekia sur la question cleaner.zip

Hello Prestashoppers, We are very excited to announce the first-ever official Prestashop meetup in India on 8th Feb 2020. Webkul is the Gold agency partner with Prestashop. Click here to check the complete info about the meetup like speakers, sponsors etc. Webkul welcomes everyone to attend the PrestaShop Meetup from the community (developers, marketers, merchants etc.) who are interested to know more about eCommerce & how we can make it better with each passing day. The meetup is open for everyone who is keen to learn more about the latest trends & developments happening in the field of eCommerce. FREE ENTRY !!! Suggest a Topic : https://forms.gle/NipNxxTYWkGEZc5z9 Share a topic of your interest that we should include in our Agenda. Become a Speaker : https://forms.gle/iRzTJrGRJ4PYkVFD7 Let us know if you want to share your expertise or knowledge about the latest trends of E-commerce. Sponsor Us : https://forms.gle/KAwmMcFg7yZqJfsZ6 For the meetup to be a success, we'll need some amazing partners. If you too hold interests across eCommerce & its various domains, we’re sure of having good times together. Limited passes are available, so register now & mark your presence at the event.

Problem solved: The issue turned out to be an error with the plugin: CAPTCHA - reCAPTCHA v1.1.7 - by ETS-Soft. I just unchecked the login page and the error went away.

Hola a todos! Espero les sirve mi solución que la busqué por cielo y tierra: Vayan al archivo: ExternalContentProvider.php En la Ruta: /modules/ps_mbo/src/ExternalContentProvider/ o src/ExternalContentProvider/ Cambien la línea 33: const TIMEOUT_SECONDS = 0.6; https://github.com/PrestaShopCorp/ps_mbo/blob/b0acf14aa81e092842ed81f95b4b91320f58618d/src/ExternalContentProvider/ExternalContentProvider.php#L33 Por: const TIMEOUT_SECONDS = 20; Espero les sirva. Saludos.

My site (running PS 1.7.6.5) uses a shipping module provided by our shipping provider, which adds the shipping price automatically based on the customer's address data. Thus, until the customer (or guest) has added their address at checkout, the cost of shipping is unknown. Instead of simply hiding this empty value (as one would expect), Prestashop shows the shipping as "Free", which is obviously misleading to the customer.
 The above solution did not solve my problem because it hides the shipping cost line forever. I want the shipping cost to show up when it is available (i.e. if the client has a registered address and the shipping module has added the price data). My solution is to hide the shipping cost (and not include it in the total) if it's 0.
 Here's how I solved the problem: (your files will vary, since I'm using a custom theme) Four files need to be modified:
 -themes/[theme name]/templates/checkout/_partials/cart-summary.tpl -themes/[theme name]/templates/checkout/_partials/cart-detailed-totals.tpl 

(for the cart and checkout pages)
 -themes/[theme name]/modules/ps_shoppingcart/ps_shoppingcart.tpl -themes/[theme name]/modules/ps_shoppingcart/modal.tpl
 (for the ajax cart preview) 1) cart-summary.tpl: replace everything inside {block name='cart_summary_subtotals'} with the following: {block name='cart_summary_subtotals'} <!--ADDED-->{if $cart.subtotals.shipping.value > 0} {foreach from=$cart.subtotals item="subtotal"} {if $subtotal && $subtotal.type !== 'tax'} <div class="cart-summary-line cart-summary-subtotals" id="cart-subtotal-{$subtotal.type}"> <span class="label">{$subtotal.label}</span> <span class="value">{$subtotal.value}</span> </div> {/if} {/foreach} {else} {foreach from=$cart.subtotals item="subtotal"} {if $subtotal.value && $subtotal.type !== 'tax' && $subtotal.type !== 'shipping'}<!--no shipping line if shipping cost is zero --> <div class="cart-summary-line cart-summary-subtotals" id="cart-subtotal-{$subtotal.type}"> <span class="label">{$subtotal.label}</span> <span class="value">{$subtotal.value}</span> </div> {/if} {/foreach} {/if}<!--END ADDED ---> {/block} 2) cart-detailed-totals.tpl: enclose the {foreach} statement with the following {if/else}, in which the {else} hides the shipping line if it's 0. <!--ADDED-->{if $cart.subtotals.shipping.value > 0} {foreach from=$cart.subtotals item="subtotal"} {if $subtotal.value && $subtotal.type !== 'tax'} <div class="cart-summary-line" id="cart-subtotal-{$subtotal.type}"> <span class="label{if 'products' === $subtotal.type} js-subtotal{/if}"> {if 'products' == $subtotal.type} {$cart.summary_string} {else} {$subtotal.label} {/if} </span> <h6 class="value">{$subtotal.value}</h6> {if $subtotal.type === 'shipping'} <div><small class="value">{hook h='displayCheckoutSubtotalDetails' subtotal=$subtotal}</small></div> {/if} </div> {/if} {/foreach} {else} {foreach from=$cart.subtotals item="subtotal"} {if $subtotal.value && $subtotal.type !== 'tax' && $subtotal.type !== 'shipping'}<!--no shipping line if shipping cost is zero --> <div class="cart-summary-line" id="cart-subtotal-{$subtotal.type}"> <span class="label{if 'products' === $subtotal.type} js-subtotal{/if}"> {if 'products' == $subtotal.type} {$cart.summary_string} {else} {$subtotal.label} {/if} </span> <h6 class="value">{$subtotal.value}</h6> </div> {/if} {/foreach} {/if} Then in the same file, add another {if/else} to change the total so that it won't include shipping if 0, but will account for any discounts/vouchers applied. (Since my site uses a comma as the decimal separator, I had to format the number accordingly here, followed by the current $currency.sign. <!-- ADDED-->{if $cart.subtotals.shipping.value > 0} <div class="cart-summary-line cart-total"> <span class="label">{$cart.totals.total.label} {$cart.labels.tax_short}</span> <h6 class="value">{$cart.totals.total.value}</h6> </div> {else} <div class="cart-summary-line cart-total"> <span class="label">{$cart.totals.total.label} {$cart.labels.tax_short}</span> <h6 class="value">{$cart.totals.total.amount - $cart.subtotals.shipping.amount|number_format:2:",":"."}&nbsp;{$currency.sign}</h6> </div> {/if}<!-- END ADDED-->
 3) ps_shoppingcart.tpl: Modify div "cart-total" as follows: <div class="cart-total"> <!-- added-->{if $cart.subtotals.shipping.value > 0} <div>{l s='Shipping' d='Modules.Shoppingcart.Shop'}: <i>{$cart.subtotals.shipping.value}</i></div> {/if}<!-- end added--> {if $cart.subtotals.tax} <div>{$cart.subtotals.tax.label}: <i>{$cart.subtotals.tax.value}</i></div> {/if} {if Configuration::get('PS_TAX_DISPLAY')} <div>{$cart.totals.total_excluding_tax.label}: <i>{$cart.totals.total_excluding_tax.value}</i></div> <div>{$cart.totals.total_including_tax.label}: <i>{$cart.totals.total_including_tax.value}</i></div> {else} <!-- added-->{if $cart.subtotals.shipping.value > 0} <div>{$cart.totals.total.label}: <i>{$cart.totals.total.value}</i></div> {else} <div>{$cart.totals.total.label}: <i>{$cart.subtotals.products.value}</i></div> {/if}<!-- END added--> {/if} </div> 4) modal.tpl: Modify the "Total shipping" and "Total" code as follows: <!-- added-->{if $cart.subtotals.shipping.value > 0} <p><strong>{l s='Total shipping:' d='Shop.Theme.Checkout'}</strong>&nbsp;<i>{$cart.subtotals.shipping.value} {hook h='displayCheckoutSubtotalDetails' subtotal=$cart.subtotals.shipping}</i></p> {/if}<!-- END added--> {if $cart.subtotals.tax} <p><strong>{$cart.subtotals.tax.label}</strong>&nbsp;<i>{$cart.subtotals.tax.value}</i></p> {/if} <p><strong>{l s='Total' d='Shop.Theme.Checkout'}:</strong>&nbsp <!-- added-->{if $cart.subtotals.shipping.value > 0} <i>{$cart.totals.total.value}<span class="subtext">{$cart.labels.tax_short}</span></i> {else} <i>{$cart.subtotals.products.value}<span class="subtext">{$cart.labels.tax_short}</span></i> {/if}<!-- END added--> </p> This is working fine for me, but may need to be modified to suit your needs. I've attached the code here as well. ps_shoppingcart.tpl modal.tpl cart-detailed-totals.tpl cart-summary.tpl

I started with PS 1.6, I used it for a few websites... then I moved to PS 1.7, I manage to use it for another few websites after dirty fixing many 500 errors and 404's because of bad path and can't find X file... I first do a local installation on a virtual machine running Linux all basic configuration as a live server like HostGator config, Bluehost, and Godaddy, we also have a few other configuration as VPS, VPS Cloud Linux and Dedicated server so that we can replicate any real possible errors... Then we moved the final product to a live server, we ran a few other test before release and we are done... The problem is that on PS 1.7.2.X + we have a problem after problem not with PS itself but with it's CORE engine symfony... Libraries out of date, libraries requiring other libraries, libraries requiring certain server configurations and so on... As I said when install a fresh out of the box no problem!... the problem is after. Each client require different setting, different payment getaways, different this, different that... I think we don't expect a bulletproof system because there is no such thing, but PS 1.6 was/is way better in my list than PS 1.7, but we also have to move on a use new technologies, but if the new is not better than the old... what use do we have... After more than 15 websites and more than 6 years of XP working with e-commerce in my personal opinion PS 1.7 is going down hill, slowly but is going... I'm moving to OC for now. Good luck.

For me PrestaShop 1.7 is worse choice remove some user friendly options is not good start or not working native modules on stable versions too.

Hi Guys, Is really sad that nobody tried to answer nothing about this issue becuase that make no sense to have a forum, so I found the solutions by myself. The problem was that Swiftmailer (What Prestashop uses for SMTP), was not able to handle my let's encrypt SSL certificated. As it seams, Swiftmailer don't accept self signed SSL certs. I found the solution on this web site: https://github.com/humhub/humhub/issues/3140 Adding next line to \vendor\swiftmailer\swiftmailer\lib\classes\Swift\Transport\streamBuffer.php $options = array_merge($options, array('ssl' => array('allow_self_signed' => true, 'verify_peer' => false))); //MFM 23/08/2019 SSL email problem Just above if (isset($this->_params['stream_context_options'])) { $options = array_merge($options, $this->_params['stream_context_options']); } Attached is the modified file. Thanks, Mauricio F. StreamBuffer.php

El problema de Prestashop estos años, es que hicieron en su momento una mala planificación en la salida de la versión 1.7 (no será ni la primera ni la última empresa que tenga este tipo de problemas), pero la idea del cambio a symfony no es mala (no está completa todavía). Desde la salida "oficial" de la 1.7 (finales de 2016) a este año, se han corregido bastante problemas, además de ir migrando poco a poco a symfony (recuerdo que la migración sigue sin ser completa todavía), y se seguirán corrigiendo, porque todavía falta un trecho. Pero estoy seguro que el resultado final que veremos, sera un salto de calidad importante en comparación con versiones anteriores. En definitiva, ¿Ha cometido un error Prestashop? Como mínimo: Sí, sacar prematuramente la versión 1.7 en su momento. Anunciar que el soporte de la 1.6 se acababa en octubre de 2018, cuando al final lo han terminado ampliando hasta finales de junio de 2019. No decir toda la verdad (estos años), sobre el uso de la 1.7 en una tienda en producción (sobre si es recomendado u no). Personas que estamos metidas en el mundillo, sabíamos la realidad, pero el usuario que entraba en la web no estaba al tanto, a excepción de que buscara información por Google. Eso sí, Prestashop decía que todo era una maravilla. Por otro lado, y es mi opinión personal, falta involucrarse más en la comunidad (por parte de la empresa). Entiendo que el objetivo de una empresa es obtener el máximo beneficio económico, pero algunos hemos ayudado a mejorar la herramienta (de forma altruista), bien sea por el foro dando soporte, otros ayudando en los repositorios de código, otros en las traducciones, etc. Sobre la decisión de webempresa, no opino, ni negativamente, ni positivamente, cada empresa decide su estrategia comercial. Y cuando ellos han decidido no seguir con Prestashop, imagino que lo han estudiado detalladamente, y no ha sido una decisión en caliente. Podemos hacer especulaciones, en base al comunicado de webempresa, pero nada más. Sin más dilación, Un saludo de @nadie

I think the problem's the Prestashop cache because I found something in "/config/defines.inc.php" http://prntscr.com/ic72b5 So I tried to delete two folders below and my site works normally now. -"/app/cache/dev" -"/app/cache/prod" Hope it could help. Thanks!

Disabling "Merchant Expertise" module fixed the problem uff

Lo primero es que veo que estas trabajando con la 1.7, cosa que yo nunca recomendaría en la actualidad, si de mi dependiera montar una tienda estaria con la 1.6 por el momento. Y ahora vamos a discutir sobre tu problema. Ya que usas la 1.7, al menos tenla actualizada, ya que de tu versión 1.7.0.5 a la 1.7.1.1 actual se han corregido muchos bugs y errores. El modulo "alertas por correo" sigue existiendo, buscalo en la pestaña Módulos -> Módulos -> Seleccion con el nombre de "mailalerts" o "ps_emailalerts" y mira ver si te aparece Adjunto Captura De todos modos, te adjunto la versión "2.0.1" del módulo. Entiendo que el unico "email" que te falla es el que tienes que recibir tu cuando un cliente te hace un nuevo pedido ¿no? Si te fallan mas emails, yo revisaria la pestaña Parametros Avanzados -> Logs a ver si ha salido alguna falla Y recomendaria configurar el envio de los emails por SMTP en la pestaña Parametros Avanzados -> Correo Electronico Saludos, ps_emailalerts.zip

Hello to all, I introduce myself as a member of the Friend of Presta association and I think many people on this forum already know me. Since a few months the FoP association has created a security cell that analyses the PrestaShop ecosystem. We have identified hundreds of modules with security holes. You can already find the list of modules for which we have already created CVEs by respecting a timeline for the authors of these modules. You can subscribe to the rss feed here this list is updated every Tuesday and Thursday. I will try to add on this post all the new vulnerabilities we publish.

PhenixSuite 1.6.2.15 : Enfin un vrai tracking par client

You can rename you whole /var/cache folder to /var/cache_old - Presta will regenerate it with next page call

Just go to modules manager faceted search -> rebuild price index... Best Regards

I don't blame just tell for problems

Try to rename var/cache to var/cache_old on your server - it will be regenerated with next shop access

SOLVED!!!! Problem was that the captcha algo has to be activated in the contactcontroller.php; 1: enter reCaptcha and generate the keys with your domain 2: Add <script src=https://www.google.com/recaptcha/api.js'></script> to header.tp just before the </head> tag 3: Add <div class="g-recaptcha" data-sitekey="[public Google key]"></div> to contact-form.tpl just before</form> tag 4: go to /controllers/front/ContactController.php and just efter this line : $this->errors[] = Tools::displayError('Bad file extension'); add: } else if (!($gcaptcha = (int)(Tools::getValue('g-recaptcha-response')))){ $this->errors[] = Tools::displayError('Captcha not verified'); } Thats it! For prestashop 1.6.1.5