JPresta Cache Warmer

You can find your invoice in your JPresta account in the "Order history and details" menu.

If you don't see it make sure you registered an address in your account so the invoice can be generated.

Unable to get cache-warmer informations from the shop (maybe the module is disabled or uninstalled): Read timed out

If you see this error in the log of the cache-wamer, that means there is a timeout when the cache-warmer retrieves the pages to warm up. To avoid this timeout, in the configuration of Page Cache Ultimate, click on "Advanced mode", then in the menu on "Options" and set a lower value for "Max execution time in seconds".

Warmup duration depends on 3 factors:

• The number of pages to generate: the first warmups generally contain a lot of pages, which is normal, and this number will decrease with each warmup
• The maximum number of bots you've defined: this is 30 by default, but you can reduce it to 5 bots to lighten the server load, but this obviously extends the time of each warmup
• Page TTFB without cache: if server response time is long without cache (> 3s), you may need to analyze Prestashop's slowness

Cache-warmer bots are probably considered as SPAM bots by your hosting provider. To make it work, you need to indicates in the settings of your hosting provider that the user-agent "JPresta-Cache-Warmer" is allowed.

Compared to the number of products and categories you have, you didn't think you'd have so many pages to generate, and that's normal!

The cache-warmer will generate the pages of your Prestashop store in different contexts. For example, you'll have one context for cell phones, another for computers, one for visitors and another for connected customers, and so on.

So the number of pages is multiplied by the number of contexts.

If your subscription includes only one warmup, then yes, you can specify the time of the warmup.

If your subscription package includes several warmups, then you can specify the start time of the first warmup, and subsequent warmups will be run at regular intervals.

JPresta-Cache-Warmer uses Amazon servers (AWS) to ensure a stable and efficient service regardless of the number of subscribers. 

If you want cache-warmer robots not to be banned by your hosting provider then you must authorize requests from the following IPS : 18.119.72.109 and 18.189.172.189

When using native Prestashop statistics, to avoid the cache-warmer to be included into the statistics just add this override in /override/classes/Connection.php:

class Connection extends ConnectionCore
{
    public static function setNewConnection($cookie)
    {
        if (isset($_SERVER['HTTP_USER_AGENT'])
            && preg_match('/JPresta-Cache-Warmer/i', $_SERVER['HTTP_USER_AGENT'])) {
            // This is the cache-warmer : don't log connection
            return false;
        }
		return parent::setNewConnection($cookie);
	}
}

Error code 524 usually means that the request to retrieve the list of URLs to generate took too long.

To avoid this error:

1. Go to the configuration of Page Cache Ultimate (or Speed Pack).
2. Click on Advanced mode and then on Options.
3. Set the option Max execution time in seconds to 90 seconds (or less if it is already 90s).

The number of pages to generate varies because the module only generates pages that either don't have a cache, have an expired cache, or have a cache that will expire within 24 hours.

You may notice periodic spikes in the number of pages to generate as the cache expires, this is normal.

The cache warmer generates the cache for pages in multiple contexts. By default, these contexts are automatically selected (recommended) based on the number of affected visitors.

Once the warmup process has completed, if you notice that the cache is not generated for you, it means your context was not included by the cache warmer. To understand why, you can check your context by opening the browser console.

• On Windows/Linux: Press F12 or Ctrl + Shift + I
• On Mac: Press Cmd + Option + I

Look for a line that says: "Page Cache Ultimate - Displaying the page with context <Your Context ID>".

Next, go to the cache module's configuration, open the Statistics menu, and find your context in the table. This should help you understand why it was not generated by the cache warmer (check the number of visits).