It would seem the heavy-handed attempt at crippling WP Engine and, by extension, millions (I think that's correct?) of WP Engine WordPress sites, has been followed through with for a second time—rather than taking the less destructive and reasonable approach of sorting out disputes via some sort of legal maneuvers.
WP Engine has rolled out a workaround.
So now we'll see if WP Engine can weather the storm, or if their massive portion of the WordPress community suffers loss of clients, loss of income, security failures, reputation costs, productivity loss, and wasted money. I, for one, stand to lose a hard-earned project that would have taken care of my family for six months and reduced stress for my small agency. The client is having second thoughts about WordPress itself. What organization would commit to a software that attacks its own users? We'll also get to see the WordPress brand and culture further tarnished and eroded.
I also suspect we'll see WP Engine win in court.
So what *was* their solution? Are they intentionally being vague so it’s harder to sabotage it?
>What organization would commit to a software that attacks its own users?
I mean that’s your characterisation, WP says they’re shutting down access due to WPE’s legal threats, which is common to do in any industry. If you get sued, you cut off everything and let the lawyers do their jobs.
Personally i’ll wait until all of this is over and see what happens.
This is getting tiresome. Man go sue each other already. Then 10min before trial there is an agreement.
Why on earth would you lose a project just because sites hosted on WPE can’t check for software updates for a few days?
I’m about to launch a site for an international non profit you’ve definitely heard of, hosted on WPE, and nobody cares that WPE is having issues. In fact, we turn off all the self updating and plugin library stuff because we have a lot of control over the site. WPE keeps turning it back on though… If you’re reading this wp engine, that sucks; let us set DISALLOW_FILE_EDIT and DISALLOW_FILE_MOD to false, permanently.
I have a hard time believing that you lost a client over this but if so, that sucks but it may be a blessing in disguise if they left because they googled WordPress and seen some negative news articles about the co-founder..
Once again though, this feels like a made up Reddit story lol.
WPE should just fork WP and put Matt to sleep.
Imagine if all WPE clients sue WP Foundation and Automattic for the disruption of the services in a class action…
I bet this would be a big loss since Matt admitted no other company currently pays the 8% fee demanded from WPE.
Sincerely, there’s no winner with this war
Just saying. Hosting is a dime a dozen. Just migrate from the hosting that is giving trouble to your business. You could migrate in just 30 min after watching a youtube video. It’s dumb to side with someone over this. Let them fight in court and stop giving them your money. If you wanna drop wordpress it’s fine. WordPress will be fine without you or any of us. It’s a great tool and this doesn’t stop it from being so.