mike-source

If it doesn’t work with WooCommerce and you are aware, a) why have you published?and b) why are you not informing people?

Seriously! Email to your customers right away, or update the blog post telling people to upgrade. I would hate to think anyone else gets caught out by this.

I disabled memcached but potentially already lost my high value client! I would understand if this mistake was made by 3rd party devs but you are a hosting company and are encouraging people to use this plugin:

https://www.siteground.com/blog/sg-optimizer-new-version/

If they are on WooCommerce and they trusted you, the same thing could happen to them. This hit a major retail client for me during the Christmas rush.

If it doesn’t work with WooCommerce and you are aware, a) why have you published?and b) why are you not informing people?

Seriously! Email to your customers right away, or update the blog post telling people to upgrade. I would hate to think anyone else gets caught out by this.

I disabled memcached but potentially already lost my high value client! I would understand if this mistake was made by 3rd party devs but you are a hosting company and are encouraging people to use this plugin:

https://www.siteground.com/blog/sg-optimizer-new-version/

If they are on WooCommerce and they trusted you, the same thing could happen to them. This hit a major retail client for me during the Christmas rush.

It is both a fact and fingerpointing! Much like I am left fingerpointing about you to my client. It just makes us all look bad!

In the meantime, since you are aware of the issue (and take it from me, it is a major issue when it occurs!) Siteground have a duty to inform anyone currently on the broken version.

I wish you the best of luck with fixing it, but you lost all my WooCommerce business due to how this has been handled. There are open threads detailing there are memcached/woocommerce problems from 4 days ago, meanwhile you have a blog post bragging about how awesome your broken plugin is. So you are actively encouraging people to upgrade.

Until it is fixed: Warn people!

Thanks.

Was shocked to find this was due to a wordpress core update and not a badly written 3rd party plugin.

WHY ARE YOU ADDING INLINE CSS AND JS TO MY HEAD TAG GTFO!!!

Such a dumb thing to add! Why assume everyone uses emojis/smilies?

Who the hell even uses emojis? Most WordPress sites aren’t aimed at children, I don’t think anyone will complain if these aren’t a default.

At the moment any dev who does view->source on my website thinks I’m a hack adding inline styles with “!important” everywhere.

Just came here excited after reading this https://blog.mandrill.com/own-your-wordpress-email-with-mandrill.html

But I’ll have to test this VERY extensively before using on any client sites… looks like it needs a bit of attention, would be good to be tested up to WP4 at least ??

Bump for same error… not sure what it does, doesn’t seem critical, but terrifies clients, currently preventing me using on production sites.