Forced on SiteGround users and not ready for production

Hello @paragondigital,

We are constantly improving the plugin and any reported issues with it are inspected in details.

Indeed, there was an issue with File-Based cache automatic purge when dynamic cache is enabled and a fix is already applied in the latest plugin version. We have also tested it with WooCommerce plugin and no incompatibilities were found.

It will be greatly appreciated if you provide more details on the above mentioned WooCommerce cache issues. You can post them in a new thread in the forum. I assure you we will investigate and make sure they are all addressed.

Thank you for your cooperation in advance!

Best Regards,
Elena

Hi Elena,

Thanks for your reply. We have had many support tickets related to this, nearly all of them ended up with SiteGround support telling us we needed to consult a web developer (we are developers) because the issue was with our sites not SiteGround’s caching. It has been a very frustrating experience and SG support wasted many hours of my and my team’s time. We’ve ended up completely disabling SG Dynamic Caching through htacess edits on over a 100 sites across multiple servers as a result. The plugin has gotten better but it still needs a lot of work and testing. We are using it on some small very static sites but that’s it.

Regarding WooCommerce, we’ve seen everything from orders not processing properly with PayPal to WooCommerce sites completely crashing when SG Caching is used. The plugin/caching doesn’t do well with anything dynamic and is terrible at discerning between things that should be cached and should not be cached.

I’ve also seen issues with log and text files getting cached and not being able to download updated versions like Gravity Forms Debug logs. Sometimes clearing the cache several times from plugin fixes the issue. If a timestamp on a file changes, the cache should not serve an older version, especially after the cache is cleared.

The addition of the automatic purge on WP events like publishing a change to a page was recently added but should have been in the very first version of this plugin. This caused numerous support issues with our clients.

I hope this helps improve the plugin.

Thanks!
Zach

The plugin handles automatic cache purge just fine and it powers about a million WooCommerce installations. This is indeed an issue with your sites and the way they are developed. Please stop Memcached if you are using it right away, some plugin extensions for Woo don’t play well with object caching and cause problems similar to what you are describing.

The plugin automatically purges the cache where pages are updated, comments are posted, etc. That’s literally the first feature it had. I would check error logs why something is blocking it form cache purging. If you want, you can open a thread in the forum with more specifics and we will dig right into it and tell you more.

Hi all,
I’m having exact same issues with Memcached specifically.
It’s crashing my sites in many ways. I understand what @hristo-sg is saying, but many sites rely on several plugins, were the only problem or incompatibility seems to be SG Optimizer plugin and its Memcached option enabled.
Las week Memchached corrupted a table from my database, Tsvetan Mitev from Siteground helped me “fix” (I put quotes because he thought that might be the issue) the database issue and recommended hiring a web developer to look further in my database for optimization. However, the issue was resolved when Memcached was disabled, and then he recommended me to turn enable it again. After a few days, site crashed again with exactly same symptoms.
I’m stuck.
Need to get rid of the SG Optimizer plugin.

Hi @srifaia,

I have become familiar with your case and actually, it is not related to our Memcached service or SG Optimizer plugin. My colleague already explained in the ticket you have opened what is causing the issue with the database and why it keeps crashing.

• This reply was modified 2 years, 7 months ago by Delyan Delov.

@delyandelov thanks for getting back, just saw the ticket and all is sorted out. Looks like it’s a database optimization problem. I’ll look for someone who can deal with this.
Thanks!

paragondigitalYES YES YES!!! Siteground Plugin causes nothing but issues with numerous WC plugins, in fact every plug in I need has issues attributed to this plugin. First I am not a tech person but I spent over two months with WC and Siteground support until they also stated “hire a web developer”. Isn’t that what the SG support is for? I should not have to hire a web developer because something on SG causes constant issue. SG pushes back as if the issue is something on the users, WC or the plugins end.. I literally had to tell them 5 separate plugin developers were not coincidentally having the same issue….”Hire a web developer”? That should be their company slogan. I should not have to hire a developer because their plugins cause issues… much less because the issue is basic functions of using plug ins.