Topics
Latest
AI
Amazon
Image Credits:Brian Ach / Getty Images
Apps
Biotech & Health
Climate
Image Credits:Brian Ach / Getty Images
Cloud Computing
DoC
Crypto
Enterprise
EVs
Fintech
Fundraising
Gadgets
Gaming
Government & Policy
Hardware
Layoffs
Media & Entertainment
Meta
Microsoft
Privacy
Robotics
surety
Social
Space
startup
TikTok
conveyance
Venture
More from TechCrunch
effect
Startup Battlefield
StrictlyVC
newssheet
Podcasts
Videos
Partner Content
TechCrunch Brand Studio
Crunchboard
Contact Us
WordPress dramawent up another pass on Wednesday after WordPress.org , the open origin web - hosting software system , banned hosting provider WP Engine from get at its resource .
Ina post on WordPress.org , WordPress co - creator and Automattic CEO Matt Mullenweg wrote that pending their legal claim , WP Engine will not have access to the platform ’s resources , such as themes and plug - ins .
“ WP Engine wants to operate your WordPress experience , they need to run their own user login system , update server , plugin directory , theme directory , approach pattern directory , cube directory , translation , pic directory , caper instrument panel , meetups , group discussion , bug tracker , forum , Slack , Ping - o - matic , and showcase . Their servers can no longer access our server for barren , ” he say .
“ WP Engine is free to offer their hacked up , bastardise simulacra of WordPress ’s GPL computer code to their customers , and they can experience WordPress as WP Engine envisions it , with them getting all of the profits and leave all of the serving , ” Mullenweg indite .
As a solvent of this mental block , sites using WP Engine ’s solutions can not instal plug - ins or update their themes .
Today in Matt destroys the WordPress residential district : you ca n’t add plugins now from the .org repo if you have a WP Engine website . And I can reassert that this is happening.https://t.co/vRd7jliVsMpic.twitter.com/9XGAtXhUoN
I want to share : https://t.co / CmCwbcxZfDhas blocked@wpenginecustomers from updating and instal plugins and theme via WP Admin — interrupt essential oeuvre for#WordPressusers , government agency , freelancers , and plugin developer . Please read : https://t.co / cE45rmvnqW
Not being able to do@WordPressupdates because of the@photomatt/@wpenginefight is incense . For a small nonprofit , being catch in the midsection of this could be high-priced if we need to migrate our sites to a new server . That money / clock time should be used for our mission .
As severalWordPress developersandadvocatespointed out , the ban also prevents WP Engine customers from accessing security updates , leaving them vulnerable .
WP Engineacknowledgedthis issue and said the caller is working on a fix .
Join us at TechCrunch Sessions: AI
Exhibit at TechCrunch Sessions: AI
“ WordPress.org has blocked WP Engine customer from updating and install plugins and base via WP Admin . There is presently no wallop on the carrying out , dependability , or security measures of your website , nor does it bear on your power to make updates to your codification or substance , ” an update from WP Engine read .
In response to the incident , WP Engine said in a post that Mullenweg had abuse his control of WordPress to step in with WP Engine customers ’ access to WordPress.org .
“ Matt Mullenweg ’s unprecedented and insupportable action mechanism interpose with the normal operation of the entire WordPress ecosystem , bear on not just WP Engine and our customers , but all WordPress plugin developer and open - origin users who depend on WP locomotive tools like ACF , ” WP Engine said .
Matt Mullenweg , chief operating officer of Automattic , has misused his controller of WordPress to intervene with WP Engine customers ’ accession tohttps://t.co/ZpKb9q4jPh , asserting that he did so because WP Engine file litigation againsthttps://t.co/erlNmkIol2 . This simply is not true . Our Cease & …
The WP Engine vs. Automattic fight
It ’s important to sympathise that WordPress powers closely 40 % of the web site on the net through different host providers , which admit Mullenweg ’s Automattic and WP Engine . user can also take the open seed project and function the site themselves , but a lot of hoi polloi choose to go with plug - and - bid root .
The battle began last week when Mullenweg criticise WP Engine publicly at a group discussion and on his blog for profiteering andcalled it a “ cancer to WordPress . ”He also alleged the caller does n’t contribute as much as Automattic does to the WordPress residential district despite both of them making about a half - billion dollar in revenue annually .
In reply , Automattic send its own cease - and - desist varsity letter to WP Engine , alleging infringement of the WordPress and WooCommerce earmark .
one by one , the WordPress Foundation , a charity created by Mullenweg to maintain WordPress as an open source project , state TechCrunch that WP Engine has offend its trademarks .
“ WP Engine has indeed break theWordPress Trademark Policy . The insurance policy states that no one is allowed to use the WordPress trademark as part of a Cartesian product , project , servicing , domain name , or company name . WP Engine has repeatedly violated this policy and the Cease and Desist missive sent to them by Automattic leave exemplar of some of the many violations , ” the foundation say in an email .
The policy was updated yesterday to include an example of WP Engine . Notably , the insurance policy does n’t cover “ WP ” as a trademark .
60 minutes after banning WP Engine from WordPress.org , Mullenwegwrote on his blogthat trademark are the centre subject . He say Automattic has been essay to sign a licensing deal with WP Engine for a retentive time . He observe that the company offered WP Engine the option to either pay a direct licensing fee or make in - kind contributions to the open source project . However , he did n’t clarify what make in - kind share would mean .
you could contact this newsman at im@ivanmehta.com or on Signal : @ivan.42
