Dimitar Petrov

Hello Leandro,

I have replicated the issue. It is caused by the fact that once the password is accepted and the session is created, the same page is reloaded without no-cache headers.

In order to resolve the issue, you could exclude such password-protected pages from the SiteGround Optimizer’s cache. This could be done using the Exclude URLs from Caching feature located under the Caching section of the plugin.

I have reported the case to our developers, so they can review it and perform further tests. If possible, the issue will be resolved in future versions of the plugin.

Best Regards,
Dimitar Petrov

You are most welcome!

Best Regards,
Dimitar Petrov

Hello,

Such issues are usually caused by limited admin-ajax.php or wp-cron scripts. If you have security-related plugins, please check them. Also, if you manually limited the scripts in question, revise the added code and temporarily remove it.

If the website is hosted on SiteGround servers, consider opening a new ticket from your User Area so we can investigate the case further. Otherwise, provide us with the errors in the browser’s console, returned when you trigger an action via the plugin.

Best Regards,
Dimitar Petrov

Hey @kaylag423,

I was unable to replicate the issue, the pages are working on my end, including the features that produced the errors displayed on your screenshots.

The recommended updates are not related to the case, you can review them in the Update section.

I would recommend you clean your browser’s cache and test using a different browser. If the issue still persists, please open a new ticket from your SiteGround User Area so we can investigate the case further.

Best Regards,
Dimitar Petrov

The file from the initial error should exist, it is registered by the plugin, and also exists on my end. The path is not generated by our plugin. If the aioseo/ directory is missing on your end, I would recommend completely reinstalling the plugin or double-checking the Linux permission and ownership of the directories in question.

Regards,
Dimitar

• This reply was modified 2 years, 10 months ago by Dimitar Petrov.

Hey @omahoung,

I have installed the All in one SEO plugin on my end but was unable to replicate the issue.

According to the error that you provided, the issue is caused by insufficient Linux file permission levels. You should check the files’ required permission by your hosting service and set them.

You can also try setting up a filter for the CSS file in question, which should be as follows.

add_filter( 'sgo_css_minify_exclude', 'css_minify_exclude' );
function css_minify_exclude( $exclude_list ) {
    // Add the style handle to exclude list.
    $exclude_list[] = 'aioseo/css/admin-bar.css';

    return $exclude_list;
}

Please note that I used the CSS handler for the last All In One SEO version, which could be different on your end.

Regarding your last question, no such issue was reported on our end.

Regards,
Dimitar Petrov

Hello,

Thank you for your feedback.

If the popup does not disappear after setting up the required option, please start a new thread so we can investigate the case further. If you are a SiteGround customer, please open a new ticket on our end.

Regards,
Dimitar Petrov

Hey @pinoooo,

The default value of the URLs is 200, but you can modify that using the following filter:

add_filter( 'sg_file_caching_preheat_url_limit', 'sgo_preheat_limit' );
function sgo_preheat_limit( $xml_urls ) {
    // Define custom limit for XML URL preheat.
    $xml_urls = 300;
    return $xml_urls;
}

The code should be added to the theme’s functions.php file.

Best Regards,
Dimitar Petrov

• This reply was modified 2 years, 11 months ago by Dimitar Petrov.

I have noticed that the path definition in the wp-config.php file is still in place. I browsed your website for a while, but no errors were returned on my end(front-end and browser’s console). It seems that you have already addressed the issue. If it still persists, please open a new ticket on our end from your SiteGround User Area so we can investigate the case further.

Best Regards,
Dimitar Petrov

Hello,

The feature in question is developed to remove version-related query strings. The convention for this type of query string composition is to explicitly define the version after an identifier like

'ver',
'version',
'v',
'mts',
'nomtcache',
'generated',
'timestamp',
'cache'

In your case, the query string is just a value. If this is an actual version, I would recommend contacting the developers responsible for this logic and requesting an explicit definition.

Best Regards,
Dimitar

Hey @griotta,

The Lazy Load feature uses the data-srcset HTML attribute, which is always assigned by the WordPress application. However, if the default HTML is modified by a specific plugin or the theme, the expected result could not be met.

I have tested your website and noticed that the data-src attributes are missing, and the images that are lazy-loaded have the mentioned attribute.

I would recommend checking with your developers why the required attributes are missing. You can also switch the theme or inspect the plugins if specific page builders have been used.

Best Regards,
Dimitar Petrov

Thank you for the update, we appreciate your feedback.

If you would like the cache to be partially flushed, you should enable the Automatic Purge feature. However, this will purge CloudFlare’s cache, too. Regarding the new feature request, we will consider this, but we cannot promise or provide an ETA.

Best Regards,
Dimitar Petrov

Hey @generosus,

Indeed the three buttons have different cleaning logic. As per your request, I have structured the information below.

Automatic Purge
When this feature is enabled, our plugin monitors specific WordPress hooks and purges the entire cache or performs a partial purge. Once such a hook is triggered, the plugin flushes the cache of:
– Dynamic Cache
– File-Based cache
– CloudFlare cache(for SiteGround users only)

Manual Cache Purge (Purge Cache button):
– Dynamic cache

Purge SG Cache button
– Dynamic cache
– Memcached
– File-Based cache
– Clears assets(minified combined CSS, JSS, etc)
– CloudFlare cache(for SiteGround users only)

If a specific cache is not flushed as expected, please post a new ticket from your SiteGround User Area and provide us with more information about how we can replicate the issue.

Best Regards,
Dimitar Petrov

Hello,

Our plugins have an auto-purge feature that is triggered upon any plugin’s version update. I have also tested the feature by updating Elementor plugin on my end, and the cache has been successfully flushed. Please note that Elementor Pro is paid solution and could have different update mechanisms, so we cannot guarantee the auto-flush after such an update.

I would recommend you always purge the cache after the plugins’ update.

Best Regards,
Dimitar

Hey @pie123,

Would you please provide us with the URL of your site? If you do not want to share such info and you are a SiteGround customer, you can consider opening a ticket in our support system.

Best Regards,
Dimitar