Dimo Dimov

Hello @pixeladas,

I conducted some tests on a standard WordPress installation (version 6.5) and I was unable to replicate the issue. I see that your website is currrently using 6.4.3 so you might consider upgrading to 6.5 and see if that helps.

It is also possible that the error is related to the specific setup of your site and one of the other components is conflicting with the Speed Optimizer. My advice is to temporarily deactivate your other website plugins one by one, testing the login after each deactivation while keeping the Speed Optimizer plugin active. Should the error continue even with all other plugins disabled, try switching to the default WordPress theme for further testing. This approach will assist you in pinpointing the component that is causing the conflict. Once you identify the problematic plugin, I recommend reviewing its settings to ensure there are no overlapping features or configurations that might be causing interference with Speed Optimizer.

Regards,
Dimo

Our Speed Optimizer has a feature that allows you to convert existing images to WebP format. However, it is important to note that woff2 and WebP files are static content, and typically their caching is managed on the server side. Therefore, caching needs to be supported on the hosting server for these files.

As mentioned earlier, if your website is hosted with SiteGround, the most efficient way to address any caching issues is through our Help Desk. Please initiate a support request from your SiteGround Client Area so we can directly inspect your web application and provide further assistance.

Regards,
Dimo

Hello @realpower,

You may consider enabling the “Automatic Purge” option in the plugin settings. When it is enabled, the plugin starts monitoring WordPress hooks and purges the entire page cache or performs a partial purge when some of them fires (i.e. upon updating a post).

If you experience further issues please reach out to us by opening a support request from your SiteGround Client Area. This will enable our team to access and inspect your web application directly and provide more targeted assistance.

Regards,
Dimo

Hello @ilgrizly,

The drop-down exclude menu only lists scripts added through the default WordPress hooks. If a script is missing from the list, you can exclude it manually using one of the filters we’ve designed for that purpose. All available filters can be found here:

https://www.siteground.com/tutorials/wordpress/speed-optimizer/custom-filters/

The following post provides guidance on how you can find the script handle:

https://www.ads-software.com/support/topic/how-to-use-sg-optimizers-filters-procedure/

Regards,
Dimo

Hello @slaffik,

Our developers are already aware of the issue and we expect it to be resolved in one of the upcoming plugin updates. While we cannot provide an exact timeline, you can keep track of the progress by monitoring the changelog of future releases.

Regards,
Dimo

You are most welcome.

As mentioned earlier, without direct access to your website, it is challenging to determine the cause of the reported behavior. Since you are a SiteGround customer, the most effective way to address this is through our Help Desk. Please open a ticket with our technical support team referencing this forum thread and provide as much information as possible – steps to recreate the issue, login credentials needed in the process, etc. This will allow us to examine your website, assess any potential issues with the Security Optimizer plugin, and propose a suitable solution.

Regards,
Dimo

Hello @spacemanspiffey,

Such issues can sometimes occur due to the unique combinations of plugins and themes that different WordPress sites use and are often a result of a conflict with another plugin. If you have another security plugin installed please make sure to disable it. Then you can try re-adding the custom login URL through our Security Optimizer plugin and enabling the 2-factor authentication.

If the issue persists please reach out to us by opening a support request from your SiteGround Client Area. This will enable our team to access and inspect your web application directly and provide more targeted assistance.

Regards,
Dimo

Hello @gustavotroisi,

Your inquiry is not quite clear and the information provided is insufficient for accurate assistance. Please provide more details so that we can better understand your issue and offer appropriate help.

If your site is hosted with SiteGround, I recommend reaching out to us by opening a support request from your SiteGround Client Area. This will allow our team to access and inspect your web application directly, enabling us to provide more targeted assistance.

Regards,
Dimo

Hello @slaffik,

The warning you have encountered is not expected. I have conducted multiple tests on test installations without being able to recreate the reported message. It is possible that the issue stems from a conflict with another plugin or theme. To troubleshoot this, you can try disabling all plugins and checking if the problem persists. If the error disappears after deactivating the plugins, you can then re-enable them one by one to pinpoint the culprit.

If your site is hosted with SiteGround, I recommend reaching out to us by opening a support request from your SiteGround Client Area. This will allow our team to access and inspect your web application directly, enabling us to provide more targeted assistance in resolving the issue.

Regards,
Dimo

Hello @jairoochoa,

Our development team is already aware of the reported issue and I can assure you that they are diligently working on a solution. While we cannot provide a precise timeframe for resolution you can expect this to be resolved in forthcoming releases.

As a temporary solution you can downgrade the Speed Optimizer plugin to version 7.4.5 where the issue is not present.

Regards,
Dimo

Hello @leticia34,

Please note that the WordPress forum is specifically for support-related queries regarding the plugin itself. Inquiries related to PageSpeed Insights cannot be addressed here.

Please reach out to us by opening a support ticket from your SiteGround Client Area. This will allow our team to access and inspect your web application directly and provide more targeted assistance.

Regards,
Dimo

The custom filters are added to the functions.php file of the currently active theme. For more information on how to properly exclude certain script/s and to find its handle, please check the following thread:

https://www.ads-software.com/support/topic/how-to-use-sg-optimizers-filters-procedure/

Regards,
Dimo

Hello Breda,

The drop-down exclude menu only lists scripts added through the default WordPress hooks. If the script is missing from the menu, you can exclude it using one of the filters we’ve designed for that purpose. All of the available filters can be found here:

https://www.siteground.com/tutorials/wordpress/speed-optimizer/custom-filters/

The following post provides guidance on how you can find the script handle:

https://www.ads-software.com/support/topic/how-to-use-sg-optimizers-filters-procedure/

If you are a SiteGround client, you can also submit an inquiry from the Help Desk section of your Client Area. This way our support team will be able to access your website, preview the code in question and assist you properly.

Regards,
Dimo

Hello @zhangxiaosong,

I noticed that your website is currently utilizing our Basic CDN service, which does not support dynamic caching. If you would like to take advantage of the dynamic cache feature, it is necessary to either upgrade to the Premium CDN plan or simply disable the basic CDN.

If you still encounter any issues after that, please open a support ticket from your SiteGround Client Area. This will allow our team to access and inspect your application and provide more targeted assistance.

Best regards,
Dimo

Hello @filippoc97,

Our plugin is fully compatible with PHP 8.2 and so far we have not received similar reports from other users. It appears that your website is hosted on a platform where the exec() function is disabled for PHP 8.2. Some hosting providers prefer to do that for security reasons.

We would recommend getting in touch with your hosting provider and discussing the issue with them.

Regards,
Dimo