All In One Cache module with Redis by @thisjrodriguez

v1.2.62026/11/12

• With the store in maintenance mode, the cache is no longer accessible to the public. Pages are served before PrestaShop checks for maintenance, so a page saved by someone testing the store (from an allowed IP address) was seen by any visitor instead of the maintenance notification. Now, with the store closed, only IP addresses allowed during maintenance are served and cached; everyone else receives the PrestaShop notification. Updating the site clears the page cache.

v1.2.32026/11/07

• Visitors who have already decided on the cookie banner will see the cached page again. Until now, with Hipresta "Cookie Consent" ( hicookielaw ) or Cookies Plus, any visitor who accepted or rejected cookies browsed without cache for the remainder of their visit (in a measured store, 1.5-2 seconds per page versus 0.3 seconds). Now, each decision has its own copy of each page: no decision, "accept all," "only necessary," and every combination of purposes; a visitor will never see another decision page (the notice, Google consent mode, and blocked modules are their own). Purging a URL also deletes these copies.
• The date and proof of consent for each visitor are not stored in the cache ( hicookielaw panel; date and hash in the C_P_COOKIE_VALUE variable of Cookies Plus, which your JavaScript reads from the cookie).
• The cache remains empty for those who decided in hicookielaw when the module hides the warning by country or the visitor's IP is on their whitelist, and for those who have a decision in Cookies Plus prior to "Revoke consents" (Cookies Plus resets it on that page). Changing that date clears the page cache.
• Updating clears the page cache.

v1.2.22026/11/03

• Emptying the combined CSS and JS no longer leaves pages without styles: their versions are key to the cache, a page painted while they were changing is not saved, and old copies are automatically deleted.
• Other modules can request a separate version of the page using $_SERVER ['ALLINONECACHE_VARIANT'] , placed before this module in ` actionDispatcherBefore (used by RKR Connectif by country 1.3.1 , whose HTML depends on the visitor). Purging a URL also deletes its variants.
• New option "Serve cache to PageSpeed" (off by default): Lighthouse receives the same page as clients and measures its actual response time.

v1.2.12026/11/02

• The "Images in WebP and mobile-friendly" option from version 1.2.0 has been removed: PrestaShop now generates WebP and AVIF images automatically (Design → Image Settings), and that's where they should be configured. Updating clears the page cache and deletes any copies that may have been made ( img/aioc/i/ ).
• "Font visualization" remains the same.

v1.2.02026/11/02

• New option "Images in WebP and scaled for mobile" (Images tab, off by default): JPG and PNG images for the store (products, categories, banners, logo) are served in WebP, and on mobile and tablet, those wider than the screen are reduced (828/1280 px). Copies are made once in img/aioc/i/ ; each generated page takes a maximum of 2 seconds to convert, and an image that wouldn't be smaller in WebP remains unchanged. In a store with large banners, the mobile homepage image size went from 4.4 MB to 1.9 MB.
• New "Font Display" option (Assets tab, disabled by default): Google Fonts with display=swap and preconnect to fonts.gstatic.com , and font-display:swap in the @font-face that don't already have it, also in the theme's stylesheets (a corrected copy is served from img/aioc/css/ ). The text is displayed without waiting for the font to arrive.
• Turning either on or off clears the page cache. Uninstalling the module deletes the copies in img/aioc/ .

v1.1.132026/11/02

• Compatible with Hipresta "Cookie Consent" ( hicookielaw ): No page is served or cached for users who have already opted into cookie settings. This module stores the decision within the PrestaShop cookie and modifies the HTML accordingly (notice, Google consent mode, blocked modules), so a new visitor could receive a page from someone who had already opted in: without a notice and with consent already granted. The page cache is cleared upon refreshing.
• Pages served from cache use Cache-Control: private, no-cache instead of public, max-age=… . The browser no longer reuses a saved page without asking: after adding to the cart or logging in, the cart and session are visible, and no intermediary proxy or CDN saves the page.

v1.1.122026/10/27

• The main image on the page (the one marked with fetchpriority="high" : homepage, product page, category) no longer loads with loading="lazy" . Previously, with both "Image Priority" and "Lazy Image Loading" enabled, the former would disable loading and the latter would apply lazy loading, causing the browser to take a long time to request the largest image (LCP). Now, the priority image and header images use loading="eager" , and lazy loading respects any image with fetchpriority="high" .

v1.1.112026/10/26

• Purging a URL (using the panel button and PageCache::purgeByUrl() ) didn't delete anything: it searched for the file without specifying the device or the bot variant that shares its name. Now it deletes all versions (desktop, tablet, mobile, and bots, including the .br extension) and normalizes the URL just like when saving.
• Purging a URL no longer resets the hit statistics for the entire cache; it is recorded in the purge log.

v1.1.102026/10/25

• The first visit after a purge (MISS) receives the same processed HTML (minified, WPO) that is saved in the cache, not the original: before it weighed more than the following ones (550 KB versus 457 KB on rekire.com ).

v1.1.92026/10/25

• The page generated at that moment (the first visit after a purge, and the PageSpeed/Lighthouse page, which never uses cache) is also compressed and has the same Content-Length as cached pages, instead of being chunked , which is why PageSpeed gives a "NO_LCP" rating. PrestaShop continues its normal process: it is buffered and sent upon completion.
• Saving a cart rule no longer clears the cache, unless it's a highlighted rule and applies to everyone: vouchers created by modules for a customer don't change any cached pages. Neither do specific cart or customer prices.
• Saving the settings only clears the cache if the key changes what the visitor sees (store name and details, logo, default language and currency, catalog mode, taxes, stock, friendly URLs, etc.).
• Each purge is recorded with its reason and the URL that launched it (the last 200, in var/allinonecache/ _purgas.log ); the panel shows the last 15.
• Deferred images (WPO): the loader starts when the document is ready and monitors the images that are added later, so those created or moved by a JS from the theme loaded with defer are also loaded (previously they would not be loaded).
• Homepage preheating: /module/allinonecache/precalentar?token=… (the URL is displayed in the panel) requests the homepage for each language on desktop and mobile. Designed to be a scheduled task every 10 minutes: if it's cached, it doesn't cost anything; if a purge cleared it, it generates it before a visitor arrives.

v1.1.82026/10/25

• The page cache is served already compressed (brotli or gzip, depending on the browser) with Content-Length and Vary: Accept-Encoding , instead of decompressing it for the server to recompress on the fly. This results in less CPU usage per visit and no chunked responses, which caused PageSpeed Insights to report "NO_LCP" in many runs.
• The .br from the previous version is deleted before the new one is added, and it is only served if it is not older than the gzip file: two versions of the same page are never mixed.
• If PHP compresses the output ( zlib.output_compression ), the page is sent uncompressed to avoid compressing it twice.

v1.1.62026/05/11

• Improved. Better error handling throughout the module.
• Fixed Several bugs have been fixed, including one when uninstalling the module.

2026/04/10
v

• Improved Optimization and configuration improvements.
• Improved: The Redis cache no longer acts on the back-office.

2026/03/20
v

• Corrected . Minor corrections.

2026/03/18
v

• New First fully functional version.