Leaderboard

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

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

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

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

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

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

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

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

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

Mare sure the iframe parameter is allowed

🧩 Introducing LD Page Builder – AI-Powered Visual Page Builder The goal of this module is to help all merchants — even without technical skills — create modern, responsive, and professional pages directly from the front-office using a smooth drag-and-drop system. ⚙️ Key Features 🧱 Full visual editor: easily add text, images, videos, buttons, products, customer reviews, and more. 🤖 AI integration: automatically generate text, blocks, or even complete pages in just a few clicks. 🎨 Modern and intuitive interface designed for fast and fluid page creation. 📱 Responsive compatibility: pages automatically adapt to all screen sizes. 🔄 Continuous improvements: the module is regularly updated with new blocks and pro features. ⚙️ Compatibility : From 1.7.2 to 9.0.1+ 💸 Three plans available to fit your needs 🆓 Free Version – perfect to explore the module, including essential blocks (text, image, video, button, etc.). ⭐ Pro Version – €14.99/month – unlock advanced blocks (customer reviews, product blocks, before/after image comparison, countdown timer…) and a store of ready-made layouts. 🤖 AI Version – €29.99/month – includes all Pro features + AI-powered text and image generation with an integrated credits system. These plans are designed for all types of merchants: from those who want simple customization to professionals looking to speed up their content creation workflow. ✅ Try the editor here: 👉 https://prestashop.ldmodules.com/content/1-delivery?ld_page_builder=1 📦 Module available here: v1.3.0-ldpagebuilder.zip We’re always open to feedback, suggestions, and improvement ideas. Our goal is to make this a must-have tool for anyone who wants to save time while keeping full control over their store design.

Bonjour, Merci, je vais regarder cela

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

Pour ceux qui sont encore sous PS 1.6 (Debian 6.1, Apache 2.4, MariaDB 10.11, PHP 7.0.33) faut‑il absolument migrer vers PS 8.x ou peut‑on rester durablement sur 1.6 avec des mesures compensatoires ? Quels impacts avez‑vous constaté sur la compatibilité des modules et surtout sur le SEO ? Merci pour vos retours d’expérience.

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

Bonjour, Nous souhaitons mettre en place une réduction par palier d'achat dans les règles paniers. Ce qui semble facile à configurer mais nous rencontrons trois problèmes ... 1 - La règle panier n'exclu pas les produits en promotions 2 - La réduction par palier s'applique à tout le panier (s'il contient 1 produit de la catégorie) et non pas juste aux produits de la catégorie. (et même les produits d'une autre catégorie avec des promotions !) 3 - Malgré ces configurations nous avons observés 25 cas sur 580 qui ont bénéficiés de la remise cumulés -10, -15 et -20%. Comment l'expliquer ? Voici la configuration mise en place : BON DE RÉDUCTION DE 10% POUR 50€ D'ACHAT (sur une catégorie spécifique) : * Montant minimum : 50 * Non-compatibilité : bon de réduction 15% et bon de réduction 20% *Sélection de produit : nombre de produits requis dans le panier : 1 Ajout d'une règle qui concerne 1 catégorie. * Priorité : 3 * Etat : validé *Appliquer une réduction en pourcentage : 10% *Exclure les produits en promotions BON DE RÉDUCTION DE 15% POUR 100€ D'ACHAT (sur une catégorie spécifique) : : * Montant minimum : 100 * Non-compatibilité : bon de réduction 10% et bon de réduction 20% *Sélection de produit : nombre de produits requis dans le panier : 1 Ajout d'une règle qui concerne 1 catégorie. * Priorité : 2 * Etat : validé *Appliquer une réduction en pourcentage : 15% *Exclure les produits en promotions BON DE RÉDUCTION DE 20% POUR 150€ D'ACHAT (sur une catégorie spécifique) : : * Montant minimum : 150 * Non-compatibilité : bon de réduction 10% et bon de réduction 15% *Sélection de produit : nombre de produits requis dans le panier : 1 Ajout d'une règle qui concerne 1 catégorie. * Priorité : 1 * Etat : validé *Appliquer une réduction en pourcentage : 20% *Exclure les produits en promotions Avez-vous une explication à nos 3 problématiques ?

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

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

Przeróbka w szablonie i np. warunek dla: {$product.quantity} < X jeżeli spełniony to wyłączy np. przycisk dodawania do koszyka.

it's a bit tricky, import works but you need to set attributes properly. During import prestashop will create the missing attributes or assing existing ones. it goes like that attributegroupname:type:position(ordering of the group);attributevalues:position(ordering of values) example: Size:radio:0;S:0 T-shirt color:color:0;RED:0 You can combine these to make proper variant: Size:radio:0,T-shirt color:color:1;S:0,RED:1 but you have to remember about position otherwise presta will create new value inside wrong group: if you want to export that you would need to make a query that combines tables like: attribute attribute_lang attribute_group attribute_group_lang product_attribute_combination I made similar query for product listing but it will require adjustments. It all depends on what structure you need.

Panowie biorę się za pisanie, sam wysyłam fv z presty i myślę że popyt będzie. Będę wrzucał tutaj demówki, kto korzysta niech testuje i daje feedback. Jak będzie wersja 1.0 to założę nowy wątek z darmowym modułem i tutaj podlinkuję.

PrestaShop 9.0.2 is now available! This second patch version represents yet another step in making PrestaShop 9 more reliable. It focuses on fixing some reported issues to provide a more stable and seamless experience for merchants and developers.View the full article

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

Hi. I like this post for free drag and drop theme and i send thank you. But how much secure is that module theme ? I want to open a new eshop.

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

As you don't describe how you removed this company name it is hard to say what went wrong. But if it is really a bug you can report it here: https://github.com/PrestaShop/PrestaShop/issues

I have a new installation of PS9.0.1 on a new Win 11 / WAMP setup. PS9 Installs OK but then Apache refuses to serve up both the shop or the back end. The installation is: WAMP Server 2.4. Server Configuration Apache Version: 2.4.65 - Documentation Apache - Loaded Apache modules Server Software: Apache/2.4.65 (Win64) PHP/8.3.28 mod_fcgid/2.3.10-dev - Port defined for Apache: 80 PHP Version: [Apache module] 8.3.28 - Documentation PHP - Loaded PHP extensions - Use of PHP versions [FCGI] 8.0.30 - 8.1.33 - 8.2.29 - 8.3.28 - 8.4.15 - 8.5.0 - FCGI mode help MySQL Version: 8.4.7 - Port defined for MySQL: 3306 - default DBMS - Documentation MySQL MariaDB Version: 11.4.9 - Port defined for MariaDB: 3307 - Documentation MariaDB - MySQL - MariaDB Win64OpenSSL_Light-3_6_0 (1) Opening https://localhost/PS produces: Hmmm… can't reach this page localhost refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED And the back end produces: Oops! An Error Occurred The server returned a "500 Internal Server Error". I am obviously new at this. What have I missed? Please help!! Very annoying Barrie

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

Ne touchez pas aux produits. Vous pouvez vider cette table et surtout: guest, connections, connection_pages, page_viewed, page_not_found

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

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

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

" localhost refused to connect" seems to be a connection issue like host definition or protocol (http / https)

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

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

Hello, did you rename or delete the install folder? Best regards,

@willsmith79052 Is this answer based on AI or real experience? Best regards.

LOL, it's so funny. "E82CV371_2C" (model number of a product I sell) was mentioned in this thread and voila - when you search for "E82CV371_2C" you now get link to this thread on the first page of google results. Completely nonrelevant search result for anyone searching for "E82CV371_2C" who is interested in the product. Still, absolutely relevant product page in my eshop is not present in the search results. Hard to understand what's wrong with Google.

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!

Salutare, Pentru noile pagini (cele care nu folosesc index.php?controller= in URL), overrides.css e incarcat din admin/themes/new-theme/css/override.css Am actualizat si raspunsul din celalalt thread unde ai gasit acel CSS de test

We are thrilled to announce the release of Hummingbird v2.0.0 Beta. This milestone is the result of a monumental effort, representing more than 320 commits, 500 file changes, 50,000 additions, and 30,000 deletions. The goal is to deliver a developer-first, lightweight, and modular theme that establishes a new standard for the PrestaShop ecosystem.View the full article

Hello, I’m introducing our Op’art IndexNow module, which helps improve the indexing of your pages on search engines and, consequently, your site's SEO. The module is available here: https://addons.prestashop.com/en/seo-natural-search-engine-optimization/88693-op-art-indexnow-improve-indexability-automatically.html IndexNow is a technology developed by Microsoft to simplify search engines' work in discovering a site's pages. Websites using this technology have a higher chance of being better indexed on search engines utilizing IndexNow.

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

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 😉

SEO is dead — long live visitor experience. Search engines no longer reward tricks or keyword stuffing. They reward how real visitors use your site. For large catalogs this means: Keep menus simple — send visitors to category pages where faceted filters make product discovery easy. Ensure speed and above-the-fold content so users see what they need right away. Add instant checkout options (Amazon Pay, Apple Pay, PayPal) and seamless cart access. Use meta titles/descriptions only to improve click-through rates in search results — they don’t drive ranking. Sitemaps are no longer essential. Search engines can crawl and discover content through internal links. They’re useful for large or complex sites, but not the foundation of SEO anymore. In today’s environment, visitor experience is the strongest SEO signal. Google tracks engagement — if your site is fast, simple, and intuitive, rankings follow.

1) In the meantime, the credit card option in back office is available for merchants from Germany, Mexico and Brazil. But you always can choose the credit card payment directly in Paypal pop-up during checkout. 2) The module doesn't impact the initial Paypal fees. Regards, Daria support 202-ecommerce

That is actually really weird. I've tested it in multiple stores, and it always in the list of your screenshot. Please reinstall the module to check if that helps.

Vale, ya me funciona. Muchísimas gracias por tu buena aportación.

I have VDS, so i can reach to php.ini. But what change i need to do exactlty? I have below line in php.ini, session.save_path = "/var/cpanel/php/sessions/ea-php56" do you suggest to change it to below one? session.save_path = "/tmp"