Plamen M
Forum Replies Created
-
Hello @axis9313,
I am glad that the site is working as expected already.
Regards,
Plamen.M
Tech Support Team
SiteGround.comHello @generosus,
I checked the case and also did several tests in different browsers (Chrome, Safari, Opera):
Step1: I added 3 items in the cart:
and
Step2: I then deleted the items and refreshed the home page several times:
During my tests, I also ttried flushing my browser cache right after I added items to the cart. Once the cookies were flushed from my computer, the cart got emptied. This shows that your site does not communicate to the server when products are added to the cart but is recording the cart items in a local cookie on the local computer.
You should check the cookie, caching and the security settings in your computer. Something might be preventing your site from deleting / updating the local cookies.
Regards,
Plamen.M
Tech Support Team
SiteGround.comHello @capitancapo ,
I see that all of the settings in the SiteGround Optimizer plugin are currently enabled. I went ahead and I enabled the Side Cart feature in the CheckoutWC plugin. I then flushed the cache of the site. Checking the health status of the site did not show any issues with the REST API:
Please, double check if you still experience the issue and if you do:
– do not make changes ti the site’s settings, so that we can recreate the issue;
– provide step-by-step instructions where can we see the reported error.Regards,
Plamen.M
Tech Support Supervisor
SiteGround.comI am very glad that the issue is resolved, @rockinaway .
Happy hosting with SiteGround! ??
Regards,
Plamen.M
Tech Support Team
SiteGround.comHello @rockinaway,
I tested the reported function on your site and after I enabled “Remove Query Strings from Static Resources”, I had to also click on Purge SG Cache. Then I also flushed the cache in my browser and reloaded the site. Following these steps, rendered your site just fine and I do not see any broken elements on it – this is how I see it after I enabled the option:
Please, clear your local browser cache and verify the result at your end also.
Regards,
Plamen.M
Tech Support Team
SiteGround.comForum: Reviews
In reply to: [Security Optimizer - The All-In-One Protection Plugin] Working fine!Hello Renzo,
We are happy to hear that you like our plugin and you are using it on your sites. I hope that you also enjoy our other plugins too.
Keep on hosting! ??
Regards,
Plamen.M
Tech Support Team
SiteGround.comForum: Reviews
In reply to: [SiteGround Migrator] works well, simple to useHello @etptword ,
Thank you for your appreciation for our plugin.
Keep on hosting! ??
Regards,
Plamen Martinov
Tech Support Team
https://www.SiteGround.com/- This reply was modified 2 years, 9 months ago by Plamen M.
I am very glad that you managed to resolve the issue, @bloke .
Enjoy our plugins.
Regards,
Plamen Martinov
Tech Support Supervisor
https://www.SiteGround.com/The https enforce function of our SiteGround Optimizer plugin does 2 things, as described:
Configures your site to work correctly via HTTPS and forces a secure connection to your site. In order to force HTTPS, (1) we will automatically update your database replacing all insecure links. (2) In addition to that, we will add a rule in your .htaccess file, forcing all requests to go through encrypted connection.
So, you should search for and replace all occurrences of your site’s domain:
https://domain.tld
or
https://www.domain.tldand replace them with your localhost’s address via https://
You should also check the .htaccess file. If the redirect continues after these steps, you should discuss this with your site developer and see where else and how https might had been configured in your site.
Regards,
Plamen.M
SiteGround Tech Support TeamHello, @bloke,
In general, you should not need any caching in a local installation of your site. So, you should better keep caching plugins disabled, as well as any caching features that your theme might be having.
Wordpress has several ways of forcing https on the site. Check if you have any local .htaccess rules. Also, check the wp-config.php file for entries related to the SSL redirects like:
define(‘FORCE_SSL_ADMIN’, true);
define(‘FORCE_SSL_LOGIN’, true);or manually defined site URLs with https in the wp-config.php file. This forum thread discusses different ways of forcing SSL support in a WordPress site, you may want to check it for other clues:
https://stackoverflow.com/questions/31888405/correctly-force-ssl-on-wordpress-via-wp-config-php
Delete the content in wp-content/cache/.
Regards,
Plamen.M
SiteGround Tech Support TeamHello @generosus,
Thank you for using our plugins and for reaching out to us.
Allow me to first jump on the easier questions:
“Also, can you point us towards your documentation explaining better your FBC feature? “
-> In general the File Based Caching preserves an HTML cache of your site pages. You can read more on the official KB page of the plugin:(1) Is FBC compatible with other major caching plugins?
-> Yes, it is – however, it is always advisable to not use the case feature in several caching plugins simultaneously. For example, if you are using CSS Minification in one plugin, switch that feature off in the others. Same is true for the File Based Caching. If you have several plugins that offer this type of caching, choose one and disable it in the others;(2) Is FBC compatible with Cloudflare and SGO Full Page Caching?
-> Yes, the File Based Caching is compatible with the Full Page Caching option in other plugins;(3) Do we need to deactivate FBC before we clear our theme’s cache? (a good example is the Avada theme, which has its own caching function)
-> A general rule of thumb is to always go about clearing all your enabled caches (including the caching in your local browser) after you make changes to the content or appearance of your site which you want to show up immediately on the front end;Now on the tough part in your post:
Since the release SGO V7.0, our website “feels” sluggish. Our website’s Clouflare caching level (% cached) has dropped and/or does not cache our website as fast as it used to.We did many tests with the plugin and our observations are just the opposite of yours – file based caching resulted in even faster site loading than just the Dynamic Caching in our plugin alone. Of course, our tests were done in our hosting environment on SiteGround servers, where even the server level caching technologies are further optimized to work in line with the caching in the SiteGround Optimizer plugin, however you should not see any “sluggishness” on your site after the caches are once generated.
I would advise you to give that a test – preserve a backup of your site’s database, then disable all of the plugins bus the SiteGround Optimizer and then check if the site is still sluggish. Then you would want to enable the plugins in your site one by one to see if the sluggish behaviour might be caused by any of the other plugins.
Regards,
Plamen.M
SiteGround Tech Support TeamHello Jens,
Thank you for your interest in our plugin.
The pre-loading feature kicks in after the cache of your site gets purged – be it when its expiration time comes or when it gets purged manually. These events include the removal of the entire cache of the Optimizer Plugin. In these cases, the pre-loading feature will start regenerating the top most visited pages in the sitemap of your site. Therefore, the feature would work in a similar manner as the one you described in WP Rocket. If your site is hosted with SiteGround, the process should be much faster than WP Rocket, because the pre-heating will take advantage of the server sided dynamic caching technologies that support our plugin on our servers also,
Still, your best option is to give both plugins a test and decide for yourself the caching of which one your site feels best with.
Regards,
Plamen.M
SiteGround Tech Support TeamHello @adaptablewebsites,
The drop-down list contains CSS Styles which are added to the code of your site through standard coding procedures. CSS Styles which were added not following the standard coding recommendations, would not show up there. For these, you need to use exclusion code filters. For these, you have to find or know the handle of the style and not the style sheet name directly.
Here is a post here which explains how you can find the handle for each one of your styles and then how to exclude it. You may also contact the developer of the theme / plugin the style of which you want to exclude and they should be able to provide you with the handle name.
Regards,
Plamen.M
SiteGround Technical Support TeamHello @pearsey ,
Try:
– renaming the local php.ini file, if you have one;
– check the wp-config.php file if there are any rules that prevent writing to files:DISALLOW_FILE_EDIT
or similar variables. Best, temporarily replace the wp-config.php with the default one for WprdPress (copying the database connection details in it, of course);
– Preserve a backup of your database. Then disable all plugins in your site except for the two: SiteGround Optimizer and SiteGround Security, then test if the functions would get enabled properly. If they do, re-enable the other plugins one by one and test enabling the functions after each enabled plugin;Let us know if any of these steps helped.
Regards,
Plamen.M
SiteGround Tech Support TeamHello @gbruzzo ,
Thank you for your feedback. We are very glad that you like our plugin and our efforts to improve its features.
Regards,
Plamen.M
SiteGround Technical Support Team