Search the Community

In the fast-paced digital landscape, the need for a lightning-fast website cannot be overstated. We all understand that a slow-loading website can frustrate visitors and harm your SEO rankings. That's why we're excited to introduce you to the Super Speed module – your key to unlocking a website that not only meets but exceeds speed expectations. At its core, the main purpose of the Super Speed module is to supercharge your PrestaShop website's performance. It's all about delivering value to you by making your online presence smoother, faster, and more efficient. The Super Speed module is now available on the PrestaShop Addons Marketplace. Download now: https://addons.prestashop.com/en/website-performance/44977-super-speed-incredibly-fast-webp-cache-seo.html Compatibility: PrestaShop 8, PrestaShop 1.7, and PrestaShop 1.6 Demo: Front office | Back office HOW SUPER SPEED MODULE CAN IMPROVE YOUR PRESTASHOP WEBSITE'S PERFORMANCE? By integrating the Super Speed module into your PrestaShop website, you will have a powerful tool designed to enhance your site's performance, and in turn, provide an array of benefits for your business. First and foremost, your website will experience a significant speed boost, ensuring that your visitors enjoy swift, responsive, and frustration-free browsing. This speed enhancement directly contributes to improved user experiences, keeping potential customers engaged and reducing bounce rates. The module's support for advanced caching solutions, including server cache, Smarty cache, and browser cache, not only accelerates page loading times but also reduces the strain on your server, potentially lowering hosting costs. The Super Speed module offers a lot of awesome features for your PrestaShop website. It optimizes images with four methods (Google Webp image optimizer, reSmush, TinyPNG, and PHP optimization script) and lazy loading, ensuring quick loading regardless of image size. Database optimization removes redundant data, enhancing database query speeds. Plus, it streamlines code by minimizing HTML, JavaScript, and CSS, contributing to faster page rendering. Additionally, GZIP compression reduces data size by up to 70%, saving on bandwidth costs, and allowing your site to handle increased traffic without costly upgrades. In a nutshell, by embracing the Super Speed module, you're investing in a faster, more efficient website that offers a superior user experience, better search engine rankings, reduced hosting costs, and optimized bandwidth usage. Your PrestaShop website becomes a high-performance asset that not only attracts and retains visitors but also drives your online business forward. Introduction Video: With over 8815+ downloads and a track record of satisfied customers, it's clear that this module delivers exceptional results. But don't just take our word for it; here's what a few of our customers have to say: Olajide A: "The module improved load time from 55 secs to 4.2 secs. and it gives us unlimited image optimizations with Lazy loads. I will highly recommend this module to anyone looking to improve web load time." Martin K: "I have found this module to be very beneficial. It has significantly sped up my website, creating a marked improvement in the user experience for customers interacting with the site. This has made browsing and shopping so much smoother for my customers. The process of converting images to WebP format was also straightforward and without issues. This has resulted in a noticeably better performance. Therefore, I can confidently recommend this module for those looking to optimize their website." Soon Kheng L: "We are very happy with your prompt after-sales service. There was a minor issue, and PrestaHero fixed it on the same day! The Super Speed module is so great. Our website's loading time and speed have improved significantly. It is so easy to install and configure, with a single click on the 'Auto configuration' button. We are happy with this product and have purchased two other modules from PrestaHero. Thanks, PrestaHero!" With results like these and a growing community of satisfied users, Super Speed is the module you can trust to take your website's performance to the next level. Download Super Speed now and start speed up your site! Have questions or need assistance? Feel free to leave a comment or contact directly to our technical support on Addons Marketplace.

Hi, I created a second prestashop 1.7 site by cloning the first one. “secret/cookie_key/cookie_iv/new_cookie_key” were not changed inside of (../app/config/parameters.php). I put both prestashops on the same server with memcached/apcu installed. but I can’t use no memcached neither apcu with both of them since each of them generates the same cache keys. DO you know what configuration changes should I do to make the cache keys different? My understanding that prestashop generates the cache keys with prefix and this prefix should be unique per each site. But I do not know what settings should be changed and how. Any help is appreciated. Thank You

Hi, I'm asking for help cause I'm out of ideas. Since December 2021, my Prestashop 1.6.1.9 started to crash and return blank pages until the website was not responding at all. I found out that there are new folders created in /cache/smarty/compile & /cache/smarty/cache, as 'root' user instead of 'www-data' (or other apache's user). After I empty the cache (file system) I get this : This folder has 0 as owner (root) : www/web/cache/smarty/compile/f4/1d My only 2 temporary solutions for this is to "chown -R www-data:www-data" all the time on /cache & /compile Smarty folders And the other solution is SQL cache instead of filesystem cache, but after a couple of days, the db is too big and I need to manually empty the cache or the site will be too slow to load

This question relates to my earlier post https://www.prestashop.com/forums/topic/636915-solved-prestashop-redirects-to-login-screen-when-accessing-some-bo-menu-items/ which I thought was resolved but isn't. I am starting a new post because some information in the old one didn't relate to the actual issue, so for more clarity here it is revised: Since moving my client site to a new hosting server (where I have a number of other Prestashop sites hosted without any problem), my client's site has problems accessing some back office menu items, namely Orders, Customers and Performance. If you click on any of these, you get redirected to the login screen. Not crashed out, just redirected. Going backwards in the browser brings us back in. For the Order page for example, the URL for the menu item is: https://www.XYZcompany.com/shop/admin/index.php?controller=AdminOrders&token=4da9c0650556eb6956c784aa1b14a2bb However, if we click on it, it becomes: https://www.XYZcompany.com/shop/admin/index.php?controller=AdminLogin&token=af3bdebf540cc4942582bb9479e49ba2&redirect=AdminOrders and redirects to the login page. But, if we copy this link directly into the browser but REMOVE the token part, it opens the Orders page correctly: https://www.XYZcompany.com/shop/admin/index.php?controller=AdminOrders Yesterday, we did this a few times. At first, after accessing the Orders page with the ex-token URL and then moving around to other menu items, when getting back to Orders we would still get redirected to the login screen. But after a while, a new token seemed to have been generated that the system was happy with and we could access Orders by clicking on the menu as normal. So I thought the issue was resolved. However, this morning we are back to the redirect, and so far I have not been able to resolve it. Any suggestions from developers with a better understanding of tokens would be appreciated. I can only find information realting to error messages about "Invalid Security Tokens" but there are no error messages for us, just the redirect. Thanks!!

Hola, tengo un problema con la cache activada de Smarty, por ejemplo con el módulo de Powerful Form Generator si está activado no me guarda ninguno de los formularios que hay, desactivado funciona. Otro caso es, por ejemplo, si modificamos algún tpl o css de un módulo sobrescribiendo en el theme carpera /modulos tampoco lo actualiza. Hemos borrado cache desde el Admin, eliminado la carpeta /var/cache/prod o dev y nada También hemos eliminado la cache del cloudFlare y tampoco ¿Sabéis de algún módulo o truco que lo pueda solucionar? Gracias !

Hi, The site runs PS 1.7.8.7 with Warehouse theme with the following settings (see screenshot): -Template compilation: Force compilation -Cache: No -LiteSpeed Cache is enabled The standard cache is disabled, why I need to empty the cache after changes to filters or adding a new item to the menu? Thanks for you help A beginner

Performance Pro - All in One Performance Pro includes image optimization (WebP), page-cache, cleaning tools, lazy loading, page optimization, HTML optimization, analytics, and more! READ MORE / PURCHASE HERE: https://addons.prestashop.com/en/website-performance/86977-performance-pro-all-in-one.html What this module does for you Performance Pro is the most advanced PrestaShop performance module on the market. The module will improve the performance of your website. Studies show that having a faster site increase the conversion rate considerably. There are numerous benefits to speed optimization, such as: Increased search engine ranking Reduced bounce rate Increased conversations Increased sales User satisfaction Higher order amounts What your customers will like Nobody likes to wait. It makes us feel like we're not a company's top priority. Consumers have even less patience when shopping online. Every second it takes your website to load, your chance of losing a customer increases. Studies show that your visitors associate the responsiveness of your site with your brand's responsiveness overall. A slow site, in other words, suggests slow customer service, slow product innovation, and slow everything else. Here are what you get with Performance Pro: Cleaning Clear smarty and SF cache Clear image cache Clear HTTP cache Clear media (CSS/JS) cache Clear XML cache Reset query cache Flush query cache Clear OP cache Delete log files from the filesystem Truncate log tables the from database Truncate e-mail logs the from database Clean up old useless data Repair tables Optimize and defrag tables Change database engine to InnoDb Delete search statistics Delete page-not-found statistics Delete connections statistics Delete unused images Delete broken images Delete empty image folders Remove temporary images Delete abandoned carts Delete expired cart rules Delete expired specific prices Resource loading Preload font links Preconnect to required origins Prefetch on hover Cache Page Cache Browser cache Lazy loading Lazy load images Lazy load iframes Lazy load videos Lazy load footer Page optimization Use passive event listeners Gzip/DEFLATE HTTP/2 push CSS Origin Agent Cluster Add noopener HTML Optimization Minify HTML Optimize attributes Defer Javascript Async image decoding Add missing image size Image Optimization Convert JPG images to WebP Convert PNG images to WebP Lossless compression of SVG images System Analytics Module Analytics Server Analytics Database Analytics Profiler READ MORE / PURCHASE HERE: https://addons.prestashop.com/en/website-performance/86977-performance-pro-all-in-one.html

Hi developers, Can anyone can tell me where I can find a code which is responsible for creating combined js file of all js files? I mean everytime in footer we can find file like v_235_a8347981273902.js which is combined js file with all of the files. I want to know where I can find function responsible for creating this code because I want to ad async parameter to this script <script> Anyone? This is even more funny because if I will put some js manually in code like in footer.tpl <script async="async" defer type="text/javascript" src="{if isset($force_ssl) && $force_ssl}{$base_dir_ssl}themes/default-bootstrap{else}{$base_dir}themes/default-bootstrap{/if}/fastjs.js?ver=1.42"></script> then in final code asyn="async" is deleted. I found out that responsible for this is function in back office "Move JavaScript to the end" because when it's set to NO then everything works but then JavaScript is not at the bottom of document so it's bad to me. I have checked minify_html.class.php, HTMLPurifier.standalone and Media.php and it looks like the answer to my question is there but I can't find any piece of code that will match my request.

Hello, I've enabled debug mode, and my website is showing that random queries that should take < 10ms to load, are supposedly taking much longer. Example query: SELECT SQL_NO_CACHE * FROM `gZ5dA1fv7y_country_lang` WHERE `id_country` = 17 from /src/Adapter/EntityMapper.php:84, says 40000~ms load time, but it's obviously incorrect as the page loaded in 3s~. Loading a page multiple times can return results such as 1.2s, 2s, 3.4s load times. Shouldn't page loads be somewhat consistent if the website isn't experiencing heavy traffic? Apc Cache is disabled since it ruins Prestashop Checkout, other forms of caching are enabled such as smarty,js/css minified etc. Thanks

So I've enabled CacheApc and the product stock wasn't changing when I changed the stock in any way. Also tried with CacheMemcached, and it gives the same result. Has anyone solved this issue? I'm tempted to hook a cache clear whenever stock is changed.

Hello, I duplicated my site to make a dev site, and that site when CacheApc is turned on changes the product stock correctly when altered through the backoffice. The original site however doesn't, when you change the stock with CacheApc the stock won't update (only in the database). In my app/config/parameters.php I have the same secret/cookie keys etc only the database is different, everything else is identical. What is the problem?!

Hi guys, we use Prestashop 1.6.1.10 and we have a strange problem hapenning. When i activate APCu or Memcache(-d) Cache, we have very fast frontend, but we can't work in the backend. For example, i go into one product and change the Meta Title. After i click save in the input field stands the old Meta Title, but in the database is the new Meta Title. When i after that disable APCu i refresh the form and see the right Meta Title. Is there a way to somehow disable cache for backend? Or move backend to separate instance? What are the best practices there? Every time to turn off APCu when i change something in shop is impossible ... Will be very thankful for you help!

Hello, So In the backoffice catalog/products, i'll go into a product and edit the stock, and it says it's worked, and the database shows that it's worked. If I refresh that same page the stock goes back to what it was before, if I open in private browsing or another browser it still says the old number. If I disable CacheApc it shows the correct number. If I reload php-fpm in a terminal it shows the correct number, I believe it's some sort of opcache issue, but if I enable opcache in the php.ini file with CacheApc off it works fine. What am I doing wrong? Thanks

Hello, Whenever I enable CacheApc in the performance section, I'll get this error in my Customer Service area multiple times per person, but it rarely happens, maybe twice a day, but sometimes there's periods of time where it effects multiple people. This is the error I receive: - 30/10/2022 - 21:04 This message is sent automatically by module PrestaShop Checkout A customer encountered a processing payment error : Customer identifier: 672519 Cart identifier: 654434 PayPal order identifier: REDACTED Exception identifier: 40 Exception detail: PrestaShop cannot validate order: Property Order-&gt;payment is empty. If you need assistance, please contact our Support Team on PrestaShop Checkout configuration page on Help subtab. If anybody knows why that'd be great. I see that there's a section to 'add a server' in the performance section, but I haven't touched it. There's a dev website on another IP on the same server that sometimes has the cache enabled too, if there's some sort of crossover bugging it; the dev site is a clone of the original with a different database.

HiHo, Cela m'éviterai en effet de devoir purger tooooute la cache (alors que je ne souhaite purger qu'une seule page), et après cela devoir la rechauffer (car le prestashop est en production.. ). Dans mon cas, lorsque j'edite des entrées blogs, cela veut dire devoir faire une cinquante ou plus de purges .. ). Pour info: J'utilise le leoblog et Jpresta. Merci d'avance pour l'information Cordialement,

Hi! I've started my journey with Prestashop 1.7.8.5 recently. Working on folders and files seems easy to understand but there is one problem I need help with. Me and my team will be working together on one project in the future. We've choose Docker as platform for developing. I thought that copying whole directory ('html' folder) and putting it on different instance of docker would just work without any trouble. I've faced few errors that I had to fix after migration but there is one type of errors that really makes everything harder. Permissions. When everything on front office works and all the modifications in code I made are visible there is still problem with random functions on backoffice side. Can't add product photos because of the errors such as : "The file could not be uploaded. No temporary folder was configured in php.ini, or the configured folder does not exist." "No route found for "GET /sell/catalog/products/image/upload/57": Method Not Allowed (Allow: POST)" Brand/manufacturer img: "The file could not be uploaded." Format is not a problem. I've tried with photos which were uploaded on first instance of Docker Prestashop. I don't know how many functions from BO have problems but I'd like to learn how to prevent such a behaviour. I've tried: After migration I've deleted all 'cache' folders. For test I've set all the files and directories with 777 permission and the error still occurs. If you have any tips, please let me know

Hi, I have a multistore with 2 stores: Store 1 : theme use is "at_auros Version 2.2.0 Leotheme Team" Store 2 : theme use is "leo_nom Version 1.0.1 Leotheme Team" When i am on store 1, the user icon and cart icon are display: But when i go to the store 2 and return on store 1 after, icons disappears: I have to clear cache for solve the problem. My compilation smarty parameters are : "Recompile templates if the files have been updated" When i turn this to : "Force compilation" everything work, but its not good for production What can i do please ? Thanks

The prestashop module ps_categoryproducts doesn't refresh translations/currency when the shop/language is changed. If loaded in english it stays in english. When changing the language afterwards to e.g. german, it still displays in english. When i delete the modules cache it resets as it should. Why am i having this problem?

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

Hi all, Just in case anyone needs, here's a tiny python script to warmup prestashop cache. It fetches all the links from the sitemap page of your site and downloads them. Usage: python warmer.py http://example.com/sitemap where example.com/sitemap is the address of your site's sitemap page. https://github.com/tonage/presta-cache-warmer/blob/master/warmer.py

Hi, Been trying to install the module 'Smartblog' and have had some trouble. I've been told to clear the cache on the back end but i am worried it will delete everything on my site. Will this happen or will it be perfectly fine? Thanks

Hello, Ajax requests started to be cached by the browser after moving to another server. for example, this can be seen when the block cart module is running with "ajax cart" option after adding products to cart when I go to the cart page, the products are not updated - I need to refresh the page. if I open the developer panel in a browser and disable the cache everything works fine it seems the problem is in the server settings prestashop version 1.6.1.23 Apache version, DB server version and php version remained the same. Thanks in advance for your advices in solving the problem

Hola Gente, Estoy teniendo un problema con las pestañas de la página del producto, adjunto foto. Al hacer clic por encima de estas pestañas se queda mostrando la descripción por defecto. no cambia quedan bloqueadas. Solo ocurre si estoy iniciado como cliente, si cierro la sesión entonces funciona. En el módulo de caché de JPresta tengo el cache desactivado para clientes cuando inician la sesión, porque no me funciona el enlace de iniciar la sesión. Llevo dando muchas vueltas pero no encuentro la solución. A lo mejor alguien ha tenido el mismo problema y sepa como solucionarlo. Versión prestashop: 1.7.6.8 Versión módulo JPresta - Page Cache Ultimate: v7.4.3 Muchas gracias SALUDOS.

Hey guys!, i have huge /cache folder in my prestashop site, not i am gonna delete that folder but what the risk of my action? previously, i clear my cache manually in /cache/smarty but the huge files is /cache/cachefs folder. Any suggest? Thanks in advance

Hola acabo de actualizar el al prestashop 1.7.6 y bueno utilizo vestaCP ahora me da un error 500 que no consigo solucionar. En modo DEBUG me saltan estos errores. Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/class_index.phpqY8cSj,/home/admin/web/miweb.com/public_html/var/cache/dev/class_index.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/class_stub.phpLeDBK2,/home/admin/web/miweb.com/public_html/var/cache/dev/class_stub.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/namespaced_class_stub.phpADZ2CL,/home/admin/web/miweb.com/public_html/var/cache/dev/namespaced_class_stub.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/class_index.phpbgvVkw,/home/admin/web/miweb.com/public_html/var/cache/dev/class_index.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/class_stub.phpmEbS2g,/home/admin/web/miweb.com/public_html/var/cache/dev/class_stub.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/namespaced_class_stub.phpJhARK1,/home/admin/web/miweb.com/public_html/var/cache/dev/namespaced_class_stub.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/class_index.php6SC8uP,/home/admin/web/miweb.com/public_html/var/cache/dev/class_index.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/class_stub.phpTbFtfD,/home/admin/web/miweb.com/public_html/var/cache/dev/class_stub.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Notice: tempnam(): file created in the system's temporary directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 258 Warning: rename(/home/admin/tmp/namespaced_class_stub.php8PiRZq,/home/admin/web/miweb.com/public_html/var/cache/dev/namespaced_class_stub.php): No such file or directory in /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php on line 264 Fatal error: Uncaught Error: Class 'Db' not found in /home/admin/web/miweb.com/public_html/config/alias.php:47 Stack trace: #0 /home/admin/web/miweb.com/public_html/config/alias.php(52): pSQL('configuration') #1 /home/admin/web/miweb.com/public_html/classes/Configuration.php(155): bqSQL('configuration') #2 /home/admin/web/miweb.com/public_html/classes/Configuration.php(209): ConfigurationCore::loadConfiguration() #3 /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php(171): ConfigurationCore::get('PS_DISABLE_OVER...') #4 /home/admin/web/miweb.com/public_html/classes/PrestaShopAutoload.php(130): PrestaShopAutoload->generateIndex() #5 [internal function]: PrestaShopAutoload->load('Db') #6 /home/admin/web/miweb.com/public_html/config/alias.php(47): spl_autoload_call('Db') #7 /home/admin/web/miweb.com/public_html/config/alias.php(52): pSQL('configuration') #8 /home/admin/web/miweb.com/public_html/classes/Configuration.php(155): bqSQL('configuration in /home/admin/web/miweb.com/public_html/config/alias.php on line 47 entiendo que es algo de los permisos por lo que he leido pero no consigo dar con la clave. Por favor ayudenme Un saludo y gracias.