kuzmanstoyanov

Hello @skirridsystems,

We’re aware of the issue where a blank page appears when trying to access the Speed Optimizer’s settings page in the network admin panel. A fix for this will be released in an upcoming version of the plugin.

Regarding the other issue you reported, I was unable to replicate it on my end. I didn’t encounter any errors when trying to save changes in Settings -> General of a subsite in the Multisite installation. I tried this with both the super-admin user and an admin user of the subsite.

At this point, I’m unable to provide additional information about this issue. If you’re a SiteGround client, please open a ticket from your Client Area and our Technical Support team will verify if the issue is indeed related to our plugin.

Best Regards,
Kuzman Stoyanov

@datastream,

Thank you for the feedback.

I passed your suggestion to the developers so they can consider adding such functionality in some of the future versions of the plugin.

Best Regards,
Kuzman Stoyanov

Hello @datastream,

The plugin is designed to transfer the uploads/, themes/ and plugins/ folders. The mu-plugins/ folder is usually utilized by hosting providers to install their own plugins and apply local rules specific to their hosting environment. These plugins and rules are generally tailored to the hosting infrastructure and are not always applicable or transferable to other hosting environments.

Best Regards,
Kuzman Stoyanov

Hello @mike8040,?

We’re not currently aware of any specific conflicts with WooCommerce, but we are willing to investigate this matter further for you.

We kindly ask you open a ticket from your SiteGround account and provide us with detailed instructions on how to replicate the issue. You may also include a link to this thread as a reference. Our Technical Support team will conduct a thorough investigation, and if they identify a bug, it will be reported to the plugin’s developers.

Best Regards,?
Kuzman Stoyanov

@jmartinm You can create the table manually by executing the following query in phpMyAdmin:

CREATE TABLE wp_sgs_log_events (
id int(11) NOT NULL AUTO_INCREMENT,
visitor_id int(11) NOT NULL,
ts int(11) NOT NULL DEFAULT '0',
activity varchar(255) NOT NULL,
description varchar(255) NOT NULL,
ip varchar(55) NOT NULL DEFAULT '127.0.0.1',
hostname varchar(255) DEFAULT '0',
code varchar(255) NOT NULL DEFAULT '',
object_id varchar(255) NOT NULL,
type varchar(255) NOT NULL,
action varchar(255) NOT NULL,
visitor_type varchar(255) NOT NULL,
PRIMARY KEY (id),
INDEX log_event_index (visitor_id, ts, activity, id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

Please, make sure to replace the prefix in “wp_sgs_log_events” with the exact prefix of your MySQL database.

If you are a SiteGround client, we advise you to open a support ticket in your Client Area. The Technical Support team will investigate if there is a specific reason why the table could not be created automatically.

Regards,
Kuzman Stoyanov

Hello @jmartinm, 

As you already noticed, the reason why the activity log isn’t displaying the events is due to the absence of the sgs_log_events table.

You can easily recreate this table by deactivating the plugin and then activating it again.

Following this, you should ensure that the feature is enabled by navigating to Security Optimizer -> Activity log -> Log Settings.

It is expected that the plugin will be logging new events after that. 

Best Regards,?
Kuzman Stoyanov

Hello @imgraeme,

“Lock and Protect System Folders” is protecting the site against unauthorized executions to PHP scripts inside wp-includes/ and wp-content/ folders.

If this feature is interfering with the functionality of a plugin, you can use exclusion filters to whitelist a script. Here’s how you can do this in your specific case:

1. Disable “Lock and Protect System Folders”
2. Add the following filter in the functions.php file of your active theme:

add_filter( 'sgs_whitelist_wp_content' , 'whitelist_file_in_wp_content' );
function whitelist_file_in_wp_content( $whitelist ) {

$whitelist[] = 'guest.vary.php';

return $whitelist;
}

3. Enable “Lock and Protect System Folders”

Please note that it’s important to disable and then re-enable the feature in order to apply the whitelisting rule effectively.

Best Regards,
Kuzman Stoyanov

• This reply was modified 9 months, 3 weeks ago by kuzmanstoyanov.

Hello @dtwx,

Thank you for the suggestion.

We’ve brought it to the attention of the plugin developers. They will consider implementing it in one of the upcoming releases. Your input is greatly appreciated.

Best Regards,
Kuzman Stoyanov

Hello @jairoochoa,

The error is typical for servers where the exec() PHP function is disabled.?

Would you please make sure the exec() function is allowed on your server??

Let us know if the issue persists after that.

Best Regards,
Kuzman Stoyanov

Hello @cesardelafuente,?

I apologize for not responding in Spanish, but please note that we only provide support in English on the WordPress forum.

I’ve attempted to recreate the reported issues on a test website, but I was unable to reproduce any of the conflicts.

Given that multiple plugins are involved, I would recommend that you open a ticket from your SiteGround account. Our Technical Support team will be more than happy to investigate further and assist you in determining the root cause.

Best Regards,
Kuzman Stoyanov

Hello @jairoochoa,?

Thank you for the report. 

I’ve attempted to recreate the issue on my end, but the different Spectra blocks displayed correctly even when all the JS and CSS frontend optimization features were enabled.

The issue might be tied to more than one plugin or to a specific usage of the Spectra blocks, which, unfortunately, I was unable to recreate.

As a troubleshooting step, you could try disabling the frontend optimization features one by one until you identify which one is causing the problem.

If you’re experiencing this issue on a site hosted on a SiteGround server, I would recommend submitting a ticket in the Help Desk for further investigation.

Best Regards,
Kuzman Stoyanov

Hello @askpet,

Issues like the one you’re experiencing are often due to conflicts between the optimization features of the Speed Optimizer and other plugins.

I was unable to recreate the issue using the free Amelia Booking and Elementor on a test website.

The most effective way to investigate this is to disable all Frontend Optimization features one by one until you identify the one causing the conflict.

Once you’ve identified the problematic feature, you should exclude the conflicting script from this optimization feature, using the appropriate exclusion filter.

Should you require further assistance, I would recommend submitting a ticket from your SiteGround Client Area. The Technical Support team will help you investigate and identify the problematic script.

Best Regards,
Kuzman Stoyanov

Hello @bjrnet21,?

I kindly suggest following the instructions provided in this thread to exclude scripts from being combined, especially if they’re not available in the exclusion menu in the WordPress backend.

Depending on how the JS script is incorporated on the page, there are various exclusion filters you can utilize:

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

If you require further assistance with this, I recommend submitting a ticket from your SiteGround account. Our Technical Support team will review the case and apply the appropriate filter to exclude the problematic script from being combined.?

Best Regards,
Kuzman Stoyanov

Hello @psykonevro,

Thank you for the report.

I was unable to replicate the issue on my end. It’s likely related to a conflict with another plugin or theme, which may be interfering with the software update checks performed by the Security Optimizer.

If you are a SiteGround client, we kindly suggest opening a ticket in the Help Desk. This will allow our Technical Support team to thoroughly investigate the case.

Alternatively, if you’re not a SiteGround client, we recommend disabling all plugins one-by-one. This will help determine if the issue is being caused by any of them.

Best Regards,
Kuzman Stoyanov

Hello @remcotolsma and @pronamic_reuel,?

Thank you both for the report.?

Indeed, we are aware of the reported issue. 

According to the latest tests we performed, the issue is only present for WordPress 6.3 sites and lower. The problem can not be replicated if WordPress is updated to the latest version.?

Our developers have been notified and they are already looking into it. A fix could be expected in some of the future releases of the plugin. 

Best Regards,?
Kuzman Stoyanov