define('WPFC_PRELOAD_NUMBER', 15);
However, I’m curious: why is this necessary if you can specify the number of pages/min to be preloaded directly in the plugin under the Preload settings?
]]>When the WPFC cached pages are created by human visitors or without the cache, the featured image sizes are correct.
So there is an issue with the WPFC cache preloading, can you help to solve it please?
The issue is represented in this screenshot:
]]>with previous versions no problem.
]]>Is this a known issue that is impacting other users? Any fix for this? Thanks!
Here is an example of the error:
[Sun Jul 11 02:25:24.109747 2021] [proxy_fcgi:error] [pid 657015:tid 139755014584064] [client XXX.XXX.XXX.XXX:0] AH01071: Got error 'PHP message: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home/user/web/mydomain.com/public_html/wp-includes/meta.php on line 1078PHP message: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 356352 bytes) in /home/user/web/mydomain.com/public_html/wp-content/plugins/wp-fastest-cache/wpFastestCache.php on line 2064'
<! - WP Fastest Cache file was created in 0.36810517311096 seconds, on 21-10-20 21:15:46 -> <! - via php ->
While others without <! - via php ->
.
They are on the same server.
What does that mean?
Thanks.
]]>