Conflictul \u00eenceput \u00een septembrie \u00eentre companiile Automattic \u0219i WP Engine a avut o continuare nea\u0219teptat\u0103 - compania Automattic, care coordoneaz\u0103 dezvoltarea platformei WordPress \u0219i catalogul oficial de pluginuri WordPress.org, a anun\u021bat crearea unui fork al unuia dintre cele mai populare pluginuri - ACF (Advanced Custom Fields), dezvoltat de c\u0103tre WP Engine, care are peste 2 milioane de instal\u0103ri \u0219i este distribuit sub licen\u021ba GPLv2. Dezvoltatorii s-au ar\u0103tat indigna\u021bi de faptul c\u0103 proprietarii WordPress.org nu doar c\u0103 au creat un fork separat denumit \u201eSecure Custom Fields\u201d, dar au \u0219i \u00eenlocuit pagina principal\u0103 a pluginului ACF pe WordPress.org cu aceasta, ini\u021biind astfel migrarea utilizatorilor la fork. <\/p>\n
This action was explained by concerns for security and the necessity to provide users with a fix for a vulnerability that remained unaddressed in the ACF version distributed through the WordPress.org directory. The announcement of the fork creation also mentions that ACF developers stated they would transition to delivering plugin updates from their website instead of through WordPress.org, but representatives of WordPress.org do not recommend that users switch to the ACF developers' proposed update system until the vulnerability in the plugin is resolved. It is claimed that the replacement of the plugin is an exceptional situation supported by legal attacks from WP Engine, the developers of the ACF plugin. In addition to addressing the vulnerability, the fork has been cleaned of ties to WP Engine services. <\/p>\n
The absurdity of the situation is that just a few weeks before, Automattic itself had blocked ACF developers' access to WordPress.org, meaning that those maintaining ACF could not publish an update fixing the vulnerability on WordPress.org, yet they placed the fix on their site and recommended installing it manually or through WP Engine's alternative directory. The update fixing the ACF vulnerability had been prepared 5 days before Automattic's announcement of the fork creation. <\/p>\n
Captarea bazei de utilizatori \u0219i a paginii ACF pe WordPress.org a devenit o continuare a conflictului dintre compania WP Engine \u0219i Matt Mullenweg, fondatorul platformei WordPress \u0219i proprietarul companiei Automattic. Din 2011, Matt Mullenweg a fost investitor \u00een compania WP Engine, dar a ie\u0219it din r\u00e2ndul investitorilor \u00een 2018, dup\u0103 ce WP Engine a intrat \u00een aten\u021bia companiei de investi\u021bii Silver Lake. Pe l\u00e2ng\u0103 dezvoltarea pluginului ACF, compania WP Engine dezvolt\u0103 \u0219i platforma de g\u0103zduire a proiectelor pe motorul WordPress<\/a>, concurent\u0103 cu WordPress.com <\/p>\n Conflictul a fost activat dup\u0103 ce organiza\u021bia WordPress Foundation a depus \u00een iunie o cerere pentru \u00eenregistrarea m\u0103rcilor comerciale \u201eManaged WordPress\u201d \u0219i \u201eHosted WordPress\u201d, care erau folosite pe site-ul WP Engine. Pe 20 septembrie, Matt Mullenweg a vorbit la conferin\u021ba WordComp critic\u00e2nd activitatea WP Engine \u0219i a publicat un articol \u00een care a explicat c\u0103 WP Engine nu are nicio leg\u0103tur\u0103 cu proiectul oficial WordPress, \u00een ciuda retoricii \u0219i marketingului WP Engine care \u00eencearc\u0103 s\u0103 conving\u0103 utilizatorii de contrariu. <\/p>\n De asemenea, s-a exprimat nemul\u021bumirea fa\u021b\u0103 de implicarea slab\u0103 a WP Engine \u00een dezvoltare - av\u00e2nd un venit de 500 milioane de dolari, compania investe\u0219te aproximativ 40 de ore pe s\u0103pt\u0103m\u00e2n\u0103 \u00een dezvoltarea platformei WordPress, \u00een timp ce contribu\u021bia Automattic este evaluat\u0103 la 3915 ore pe s\u0103pt\u0103m\u00e2n\u0103. \u00cen articol, WP Engine a fost comparat cu o tumor\u0103 canceroas\u0103 \u0219i s-a men\u021bionat c\u0103 pentru a continua afacerea, WP Engine va necesita acum o licen\u021b\u0103 pentru marca comercial\u0103 WordPress. Linkul c\u0103tre articol a ap\u0103rut \u00een widgetul de \u0219tiri din panoul de administrare pe toate instal\u0103rile WordPress, inclusiv cele din g\u0103zduirea<\/a> WP Engine. <\/p>\n Pe 23 septembrie, compania WP Engine a trimis lui Automattic o cerere oficial\u0103 de \u00eencetare (Cease and Desist) pentru a opri afirma\u021biile false, \u00een\u0219el\u0103toare \u0219i def\u0103im\u0103toare. Ca r\u0103spuns, compania Automattic a cerut WP Engine s\u0103 \u00eenceteze utilizarea m\u0103rcii comerciale WordPress \u0219i a modificat regulile de utilizare a m\u0103rcilor comerciale, men\u021bion\u00e2nd numele \u201eWP Engine\u201d ca exemplu de inducere \u00een eroare a utilizatorilor prin stilizarea sa ca un motor oficial WordPress. <\/p>\n Pe 25 septembrie, accesul la resursele distribuite prin site-ul WordPress.org a fost blocat pentru WP Engine, inclusiv accesul la actualiz\u0103ri cu remedieri de vulnerabilitate, pluginuri \u0219i teme. \u00cen aceea\u0219i zi, conturile angaja\u021bilor WP Engine au fost blocate \u00een catalogul WordPress.org, ceea ce le-a \u00eempiedicat s\u0103 publice actualiz\u0103ri pentru pluginul ACF. Pe 27 septembrie, blocarea accesului WP Engine la resurse a fost par\u021bial ridicat\u0103, dar a fost reluat\u0103 pe 1 octombrie. <\/p>\n