Pavel Dosev
Forum Replies Created
-
Hello @ekapon,
I checked the site https://www.kohtaocompleteguide.com/ and its frontpage and on other pages all the images are in webp format: https://prnt.sc/E2jZ1bCSZtYsHello @micheletenaglia and @slaffik,
The error was resolved in the SG Optimizer release less than a month ago. The warning should no longer be showing for PHP 8.2 and 8.3. The warnings you are seeing are probably from previous entries or before the plugin was updated to its latest version.Hi @mitavazatakiya,
I checked the provided page, and the images are loading correctly on my end. Purging the SG cache removes any stored cache for the site, which means that the website will load the resources directly from the server. By just purging the cache, nothing is removed except the cached content.
If the problem still persists, the issue might be elsewhere. You can check the Enable Browser-Specific Caching option and see if it helps. You can also try switching off any frontend optimizations that you might have enabled in case they are causing this.
Hi @tijmensmit),
To check this further, we need more details on which specific scripts you want to show up under the ‘Exclude from JavaScript Minification’ list. This will help our developers check them thoroughly and give you the necessary feedback on what needs to be done.
Hello @donquicky,
The timestamp indicating when the IP was blocked is derived from the server’s current time using PHP’s
time()
function. While minor discrepancies can occur due to differences in user and server timezones, a significant difference like the one you’re seeing is unlikely to be caused by timezone variations alone.Unfortunately, without the ability to recreate the issue, it’s challenging to pinpoint the exact cause. However, since the timestamp is based on the server’s time, it’s possible that a temporary misconfiguration or a glitch led to the future timestamp in this particular entry.
Hello @gwmbox,
Thank you for your suggestion. We will forward your request to the plugin’s developers for consideration.If this feature is approved and implemented, it will be added in the changelog.
Any change made should purge the cache automatically, including on all the pages. If the problem still persists, we can investigate further. However, we will need access to the website. To proceed, please submit a support ticket through Siteground’s User Area.
Hello @rolfvanes,
The plugin will purge the cache when any change is made to a product and its information is updated. This includes changes to the product description, quantity, stock status (in stock or out of stock), and publication status (published or not). These changes will trigger an automatic cache purge.
For adding custom role capabilities, you can refer to the article below. It provides a custom filter on how to add purge cache capabilities to different user roles:
Control which user roles have permission to do a manual cache purge
Hello Steve,
The lock and protect feature of the plugin adds the following rules in a .htaccess file in the wp-content folder:
# SGS Directory Hardening
<FilesMatch "\.(?i:php)$">
<IfModule !mod_authz_core.c>
Order allow,deny
Deny from all
</IfModule>
<IfModule mod_authz_core.c>
Require all denied
</IfModule>
</FilesMatch>
# SGS Directory Hardening ENDAs you can see, it blocks all requests for PHP files. If you would like to allow access to this specific file you can add the rules below to the .htaccess file:
<Files "3d-secure-form.php">
<IfModule !mod_authz_core.c>
Order allow,deny
Allow from all
</IfModule>
<IfModule mod_authz_core.c>
Require all granted
</IfModule>
</Files>The whole file should look like this:
# SGS Directory Hardening
<FilesMatch "\.(?i:php)$">
<IfModule !mod_authz_core.c>
Order allow,deny
Deny from all
</IfModule>
<IfModule mod_authz_core.c>
Require all denied
</IfModule>
</FilesMatch>
# SGS Directory Hardening END
<Files "3d-secure-form.php">
<IfModule !mod_authz_core.c>
Order allow,deny
Allow from all
</IfModule>
<IfModule mod_authz_core.c>
Require all granted
</IfModule>
</Files>Hello @erikmolenaar,
Thank you for your suggestion. We will forward your request to the plugin’s developers for consideration.If this feature is approved and implemented, it will be added in the changelog.
Hello @yard
The Memcached and dynamic cache features of our plugin are specifically designed to work on SiteGround servers, as they are tied to our unique settings and configurations.
However, you can still use Memcached for your website on your current host. The only limitation is that it won’t be manageable through our plugin.Hello benjacobs04,
Could you please provide us with the file extension? The image is not loading and shows 404 when attempting to load it as PNG, JPEG, JPG, GIF, or BMP. Another thing that might be causing this is if the image is PNG and is above 512 KB. In such cases, we skip the image and do not optimize it.
Also, I see that your website is with us. If a single image is not generated, it will be easier to check if we can access the website, especially if it is in some corner case. If the image is below 512 KB and exists on the account, you can submit a ticket to us so we can check what might be preventing the web image generation.Hello @1256a987,
We cannot reproduce this on a default WordPress where the site works with SG-Optimizer and all the PHP8.x versions we are providing.
It is most likely that another plugin on the site is causing this. You can enable debug or create a staging copy of your site, where you can freely disable plugins and make adjustments and tests to the site without compromising your live site.The latest update of the plugin did not include a fix for the reported problem.
When a topic is reported to our developers, we mark it as resolved. We have a case logged for it in our internal system, which we track, and we will update the thread when the issue is resolved.
There isn’t a custom filter to stop the dynamic cache for an admin user, as our plugin does not cache the admin page and logged-in user content; hence, there is no need to add a turn-off custom filter for the dynamic cache.Hello @rajkiranb,
You can try excluding the inline script from the SG-optimizer combination by using our custom filters:
https://www.siteground.com/tutorials/wordpress/speed-optimizer/custom-filters/#Plugin_Compatibility
add_filter( 'sgo_javascript_combine_excluded_inline_content', 'js_combine_exclude_inline_script' );
function js_combine_exclude_inline_script( $exclude_list ) {
$exclude_list[] = 'window.SureCartAffiliatesConfig = {';
return $exclude_list;
}
If the problem persists, it would be better to submit a ticket to our support team through the User Area with additional details on how to recreate the issue. We can then check it on the website itself.