WordPress.org bans WP Engine, blocks it from accessing its resources | TechCrunch
techcrunch.com
WordPress drama went up another notch on Wednesday after WordPress.org banned hosting provider WP Engine from accessing its resources.

The blocked resources in question? Automatic security and features updates and plugin/theme repository access. Matt Mullenweg reasserted his claim that this was a trademark issue. In tandem, WordPress.org updated its Trademark Policy page to forbid WP Engine specifically (way after the Cease & Desist): from “you are free to use [‘WP’] n any way you see fit” to a diatribe:

The abbreviation “WP” is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is “WordPress Engine” and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress.

https://techcrunch.com/2024/09/26/wordpress-vs-wp-engine-drama-explained attempts to provide a full chronology so far.

Edit:

The WordPress Foundation, which owns the trademark, has also filed to trademark “Managed WordPress” and “Hosted WordPress.” Developers and providers are worried that if these trademarks are granted, they could be used against them.

  • @saltescEnglish
    6•3 months ago

    I haven’t done web work for well over a decade and recently was surprised to learn that Wordpress is still very relevant. I remember back then, seeking alternatives as we expected it to become more of a legacy thing a few years down the track, so we were on the lookout for future-proofing client sites with a better foundation. At that point it was a decade old and annoying af because it morphed into a messy way of doing websites because people misused it’s original purpose. Brain had to think like a blog and then trick it into doing what you want, kind of like using tables to structure pages before CSS-P saved the day.