ArtBoyle

@joost de Valk:
If you read all the posts here and elsewhere you will see that many people are saying their sites were broken by this update.

I know you do a lot of very good work, however, when experiencing this kind of an event, denial is an urge you should steer clear of, just my opinion, I personally really like your products.

Yes I definitely agree, everyone has a responsibility to test plugins before going live, yours recent update is dramatic proof of that wisdom.

Joost de Valk,

Well the attitude seems quite cavalier to me and many other users I have talked to. You broke peoples sites. Worse than that you broke their clients sites and made them look bad.

I tested on one of my own sites before my clients and abruptly found out that the new code took my site down unless I turned off my CDN (Probably a java issue). I can only image doing this to my larger clients!

Basically you are now like Microsoft drivers, anyone with a brain does not trust MS to update their drivers at will. Now many don’t trust you, I know I don’t.

Using Yoast SEO now for some, not all, will mean set it up, get it working and never update or upgrade it and perhaps look for an alternative product.

Even though you made great products, the perception of rushing to monetize all the features before they are ready does not have good optics. Basically when you shoot yourself in the foot you get another chance, but when you shoot yourself in the head, well its over.

You have opened the door very wide for your competitors, you need to find a way to close it fast.

Thanks for your help, I executed the tests you recommended and found that the plugin was trying to work but was being blocked. After discussion with my hosting providers and based on the article you directed me to I had them do a check and they had changed the crone permissions “accidentally” and have since reversed that and now the plugin works as it should again (at least on one of the 2 sites, still looking at the other one).

Thanks for your help!