WP Rocket
Forum Replies Created
-
Forum: Plugins
In reply to: [Heartbeat Control] DEBUG.LOG error: heartbeat.php on line 79Hi,
Sorry for the delay.
Please update to 2.0 version. The plugin has been totally rewrite.
Best
Forum: Plugins
In reply to: [Heartbeat Control] Heartbeat Control settings with Woocommerce storeHi!
Sorry for the delay.
The value depends to the CPU usage you can have on your website.
For a WooCommerce website, I will suggest you to not disable Heartbeat on front-end.
Best
Forum: Plugins
In reply to: [Heartbeat Control] PHP 7 compatibility shows an error nowHi,
Sorry for the delay.
The plugin has beed totally rewrite in 2.0 version.
Please update to the new version, it must fix your issue.
If not, please let us know 🙂
Best
Forum: Plugins
In reply to: [Heartbeat Control] Another error after updateHi,
Please note that OPCache isn’t related to your web server: Apache, NGINX or Litespeed.
It’s related to your PHP configuration. The issue you have is mandatory related to OPCache. You have an old file which try to load a file which doesn’t exist anymore.
If you want a quick solution, it will be to totally delete Heartbeat Control and re-install it.
Best
Forum: Plugins
In reply to: [Heartbeat Control] Error after updateHi,
Sorry for the inconvenience.
Can you please tell me if you have Heartbeat Control activated from the network or site by site?
Best
Forum: Plugins
In reply to: [Heartbeat Control] Another error after updateHi there,
It seems to be an issue related to OPCache.
Can you please check if you have OPCache on your server? If so, you will have to purge OPCache to fix the issue.
Best,
Hi,
The only solution currently would be using the
DONOTLAZYLOADconstant or thedo_rocket_lazyloadfilter. We don’t currently have a way to prevent lazyload from URL parameter or User Agent.Hi,
Our lazyload only works for images, iframes, and elements using an inline background-image. It can’t be used to lazyload other elements.
Hi,
Our plugin doesn’t set any alt attribute for images, it uses the attribute defined for the image initially. You have to define the alt yourself if you want it to be there.
Hi,
Those images are set as background images in external CSS files, so they can’t be lazyloaded. The lazyload requires the images to be set in the page HTML directly to be applied.
Hi,
This is related to the native lazyload in Chrome. To optimally lazyload and preserve layout, width and height attributes of the images should be defined on the image element. The lazyload still works correctly though.
Hi,
Thank you for reporting this, we will look into it to release a fix in a future version.
Hi,
Do you determine it was specifically linked to the lazyload plugin? Do you have a different result when it’s disabled?
Hi,
If you’re using WP Rocket, please open a support ticket directly for it through the Beacon or the support page on our website.
This forum is for support of the lazyload plugin only.
Thank you
Hi,
Do you have an URL we can check to see what could be happening?