Gergana Petrova

Hello @pinoooo,

There should be no issues experienced if you disable the Rest API for Non-logged in users/Non-Admins.

Still, in case further assistance is needed – you can submit a new ticket from your Client Area within SiteGround, so our team can take a closer look on your behalf.

Best Regards,
Gergana Petrova

Hello @thosethingstheysaid,

If you have transferred the site’s content away, the best approach would be to deactivate the plugin and login using the Default admin URL. Once logged in, you can reinstall the plugin and configure the Custom admin URL a new.

In case you’re using external CDN proxy only and the content is still hosted with us, you should temporarily disable the proxy which should allow you to access via SiteTools link directly.

If the SiteTools link is not working even after that, please submit a support ticket via your SiteGround Client Area, and use this topic as a reference, so we can further assist you.

Best Regards,
Gergana Petrova

Hello @bouncern,

The issue is related to the cookiehash constant. Within a Multisite, the cookiehash constant is being defined, but only as of the main site URL.

Our developers are aware of this and are working on a fix. While we cannot provide an ETA, as soon as it is ready we will deploy it in a new SiteGround Optimizer version. You may monitor the Changelog of future versions for the purpose.

A temporary fix for this will be to disable the File Caching for the specific subsite of the network.

Best Regards,
Gergana Petrova

Thank you for the update, @mammadz.

Could you please provide us with the domain name of the site and a couple of example pages for which you believe the Preheating is not working.

If you’re a SiteGround customer, please submit a support ticket from your Client Area, providing this topic as a reference and again a few example pages. This will allow our team to double-check your configuration and review the server’s logs if needed.

Best Regards,
Gergana Petrova

Hello @generosus,

The code snippet has already been provided in a different thread, which I am linking bellow, for reference to other users:

Help Needed | Creating WP Filter to Purge SG Optimizer Cache

As for the advice provided by our developers, it relates to this particular case and the SiteHealth check status specifically, if one needs to obtain its stats manually while utilising Memcache.

The recommended setting for the Heartbeat in the backend, is indeed to be Disabled, as in our experience – it is not essential as a function for a larger number of WordPress websites.

Thank you for the feedback on the matter.

Best Regards,
Gergana Petrova

Hello @generosus,

The case was reviewed by the Developers team and I would like to offer some additional information about the issue at hand.

Information for the health check is stored as a transient. Transients are stored into the object_cache when such is being used. ?The cache flush deletes the transients and they can no longer be accessed unless re-generated.
?In order to have the health check information generated and stored as a transient, the WP Heartbeat needs to be enabled and the Site Health screen:?wp-admin/site-health.php must be accessed. Another option for the stats to be re-generated is the cron job:?wp_site_health_scheduled_check to be executed, as you already mentioned in one of your previous replies. Still the check is being run once a week only.

So instead of disabling the Memcache service, the above can be summarised as follows:

?1. To get the stats manually, you must:
? Enable Heartbeat for the admin pages.
? Once the cache is flushed, go to the admin Site Health page directly

2. To get the stats automatically, you may consider creating a custom code snipped which will run the?wp_site_health_scheduled_check cron event every time the SiteGround Optimizer plugin cache is flushed.

When the cache is flushed we are calling “do_action” request which can be used for this case. The hook used is:?siteground_optimizer_flush_cache.

For the moment no modifications will be made on how the plugin is working, but we thank you for the feedback and will have this in mind for future releases.

Best Regards,
Gergana Petrova

Hello @generosus,

Thank you for the feedback and suggestion. It has already been forwarded to our developers and it will be further reviewed.

If approved, it can be expected in one of our future releases.

Best Regards,
Gergana Petrova

Hello @daveporter,

I have brought your suggestion to the attention of our Developers.

While we cannot provide an ETA and a guarantee the changes will be implemented, you may follow the Changelog of future plugin versions.

Best Regards,
Gergana Petrova

Hello @christosbale,

I was able to resolve the issue by excluding Woocommerce media type from Media >> Media Optimization >> Exclude Media Types from Lazy Load, within the plugin’s configuration.

I have also brought the issue to the attention of our developers, who can further review it on their end, in order to determine what caused the duplication in the first place and if there’s a way to avoid entirely, without using the Exclude functionality.

While I cannot provide an ETA for a possible fix or new release, you may follow up on this by checking the Changelog for each new version.

Best Regards,
Gergana Petrova

Hello @adriders,

Thank you for the suggestion. I have brought your request to the attention of our developers, who will further review it.

While I cannot provide an ETA or confirm the feature request will be fulfilled – you may keep an eye out for new versions and the changelog.

Best Regards,
Gergana Petrova

Hello @hiddenpearls,

Since we haven’t heard back from you in the past couple of days we will be marking the topic as Resolved.

You will still be able to post a reply in case further assistance is needed.

Best Regards,
Gergana Petrova

Hello @fernandot,

Since we haven’t heard back from you in the past couple of days we will be marking the topic as Resolved.

You will still be able to post a reply in case further assistance is needed.

Best Regards,
Gergana Petrova

Hello @remcotolsma,

A fix for the reported issue has been deployed and is available since version 7.1.3, most recent version is 7.1.4. Please update the plugin to the latest version and test on your end as well.

Best Regards,
Gergana Petrova

Hello @generosus,

The Lazy Load exclude option using URL is available since version 7.1.3, for the moment however it happens via filter:

add_filter( 'sgo_lazy_load_exclude_images', 'exclude_images_from_lazy_load );
function exclude_images_from_lazy_load( $excluded_images ) {
    // Add the src url of the image that you want to exclude from using lazy load.
    $excluded_images[] = 'https://mydomain.com/wp-content/uploads/your-image.jpeg';

    return $excluded_images;
}

I have also passed your requests to the attention of our Developers, for further review.

While we cannot provide an ETA and if they will be implemented, you may follow the Changelog of future versions.

Best Regards,
Gergana Petrova

Hello @animesubways,

Since we haven’t heard from you in the past couple of days we will be marking the topic as Resolved.

You will still be able to post new replies if needed.

Best Regards,
Gergana Petrova