Bidh Automattic a’ toirt air falbh liosta teachdaiche einnsean WP bho làrach Tracker

Thug Automattic air falbh cliath-dhuilleag anns an robh ainmean fearainn luchd-ceannach WP Engine bho làrach-lìn WP Engine Tracker. Tha an toirt air falbh mar fhreagairt do òrdugh tòiseachaidh a chaidh a thoirt do WP Engine, ag òrdachadh Automattic agus Matt Mullenweg an spreadsheet a thoirt air falbh taobh a-staigh 72 uairean.

Chaidh fàilte chridheil a chuir air a’ bhacadh tòiseachaidh air X (Twitter roimhe), a tuiteadh le riochdaire Joe Youngblood den bheachd coitcheann:

“Bha an riaghladh na bhuannachadh mòr dha gnìomhachasan beaga agus luchd-tionnsgain a tha an urra ri stòr fosgailte a’ cumail ris na geallaidhean aca. Tha sin a’ toirt a-steach leigeil le webhosts aoigheachd a thoirt do agus gun a bhith a’ goid stòran còd.

Tha mi an dòchas gum bi làn thoradh an search engine marketing a’ coimhead automotive coltach ris.”

cuideigin eile tuiteadh:

“Tha pàrtaidhean neo-chlaonach a tha a’ coimhead air an taobh den bheachd gun d’ fhuair a’ chùirt ceart. Bha search engine marketing follaiseach bhon chiad latha.

Is e an ath cheum dhutsa feuchainn ri socrachadh a-mach às a’ chùirt gus casg a chuir air tuilleadh nàire agus gus cunnart milleadh a lughdachadh.”

Connspaid Mullenweg le einnsean WP

Thòisich Matt Mullenweg ionnsaigh an-aghaidh Einnsean WP air 20 Sultain, 2024 às deidh dha WP Engine diùltadh deichean de mhilleanan dolar a phàigheadh, rud ris an canadh neach-lagha WP Engine “iarrtasan airgid uamhasach” ann an litir stad is stad a chaidh a chuir gu Prìomh Oifigear Laghail Automattic air 23 Sultain. .

Air an t-Samhain sixth chuir Automattic an cuideam air WP Engine le bhith a’ cur air bhog làrach-lìn leis an t-ainm WP Engine Tracker a bha a’ tabhann liosta de luchd-ceannach WP Engine a dh’ fhaodadh luchd-aoigheachd lìn eile a chleachdadh gus tairgsean iarraidh air luchd-dèiligidh WP Engine fhàgail.

Tha e coltach gun lean iarrtas luchd-ceannach WP Engine, mar co-cheangailte le Redditor ann an deasbad mu làrach-lìn WP Engine Tracker:

“Bha mi a-mach às an oifis airson cuid de mhodhan meidigeach, agus mar sin chaill mi an rud WPE Tracker. Ach, tha search engine marketing a’ mìneachadh carson a fhuair mi fiosan aoigheachd gun iarraidh bho ghnìomhachdan sònraichte. Gu soilleir, tha cuideigin ga mhèinneadh gus gnìomhachas a shireadh. Gu tur a’ fàs nas miosa agus cuideachd gu tur an dùil.

Tha search engine marketing uile a’ dèanamh barrachd dhomh air WP Engine. Deagh obair, Matt, tapadh leat.”

Thàinig làrach-lìn WP Engine Tracker gu bhith na fhianais air a’ chron a rinn Mullenweg air WP Engine agus chaidh a ghairm anns an iarrtas airson ro-òrdugh.

Thachair am britheamh le WP Engine agus thug e seachad an òrdugh tòiseachaidh, ag iarraidh am measg mòran de rudan eile gun toir Automattic agus Mullenweg sìos an liosta de luchd-ceannach WP Engine.

Tha òrdugh na cùirte ag ràdh:

“Taobh a-staigh 72 uairean, thathar ag iarraidh air luchd-dìon:

…(a) thoir air falbh an liosta de luchd-ceannach WPEngine a tha san fhaidhle “domains.csv” ceangailte ri làrach-lìn luchd-dìon wordpressenginetracker.com (a chaidh a chuir air bhog air no mu dheidhinn
7 Samhain, 2024) agus air a stòradh anns an stòr GitHub co-cheangailte ris a tha suidhichte aig https://github.com/wordpressenginetracker/wordpressenginetracker.github.io.”

Chaidh am faidhle CSV a thoirt air falbh às deidh sin ged a bha an ceangal gu faidhle nach eil ann , le ceangal a’ sealltainn neoni :

Glacadh-sgrìn de Làrach-lìn WP Engine Tracker

Ma bhriogas tu air a’ cheangal thig teachdaireachd freagairt mearachd 404.

Glacadh-sgrìn de 404 Freagairt Mearachd Airson Luchdaich sìos CSV

Tha iarrtas tarraing air GitHub a’ sealltainn gun deach iarrtas a dhèanamh gus am faidhle CSV a thoirt air falbh air 11 Dùbhlachd.

“Thoir air falbh CTA gus liosta de làraich #29 a luchdachadh sìos

thuirt wordpressenginetracker 9 uairean air ais
Bidh am PR search engine marketing a’ toirt air falbh an teacsa agus an ceangal luchdaich sìos gus an liosta de làraich a tha fhathast a’ cleachdadh WPE a luchdachadh sìos.”

Glacadh-sgrìn Of GitHub Pull Request

Plugin Superior Customized Fields

Thug Automattic air falbh am plugan WP Engine’s Superior Customized Fields (ACF) bho stòr-dàta oifigeil plugan WordPress.org agus chuir e dreach clonaichte Automattic na àite, air ath-ainmeachadh mar Safe Customized Fields (SCF).

Tha an òrdugh-cùirte tòiseachaidh ag òrdachadh Automattic cuideachd cothrom fhaighinn air ais gu stòr plugan Superior Customized Fields (ACF):

“Taobh a-staigh 72 uairean, thathar ag iarraidh air luchd-dìon:

…(v) a’ tilleadh agus ag ath-nuadhachadh ruigsinneachd WPEngine air agus smachd air an liosta eòlaire plugan Superior Customized Fields (“ACF”) aig https://wordpress.org/plugins/advanced-customfields, mar a bha e air 20 Sultain, 2024. ”

Tha am plugan clonaichte SCF fhathast ann aig an URL sin, ged a tha ùine aig Automattic fhathast a thoirt sìos.

Glacadh-sgrìn de SCF Plugin ann an Liosta Eòlaire ACF

Ìomhaigh sònraichte le Shutterstock/tomertu


#Bidh #Automattic #toirt #air #falbh #liosta #teachdaiche #einnsean #bho #làrach #Tracker


Search Engine Journal


#Bidh #Automattic #toirt #air #falbh #liosta #teachdaiche #einnsean #bho #làrach #Tracker


Roger Montti , 2024-12-12 10:17:00

Decide Sides With WP Engine In opposition to Automattic & Mullenweg In WordPress Dispute

A choose dominated in WP Engine’s favor of their request for a preliminary injunction in opposition to Automattic and Matt Mullenweg. The courtroom agreed that WP Engine will endure irreparable hurt if the injunction is just not granted and giving the defendants (Automattic and Mullenweg) 72 hours to return issues to the way in which they had been as of September twentieth, 2024.

The choose dominated in opposition to Mullenweg and Automattic on each argument, granting WP Engine a preliminary injunction. The ruling requires the defendants to revive WP Engine’s entry to WordPress.org, regain management of the WordPress.org listing itemizing for the Superior Customized Fields (ACF) plugin, and take away a listing of WP Engine clients from the domains.csv file linked on the wordpressenginetracker.com web site.

There have been six elements labeled A – F that define the choose’s evaluation of the case:

A. Success on the Deserves

B. Irreparable Hurt

C. Steadiness of Equities

D. Public Curiosity

E. Bond

F. Scope of Injunction

A. Success on the Deserves

On WP Engine’s “declare for tortious interference with contractual relations” the choose dominated:

“Defendants’ arguments in opposition don’t compel a unique conclusion.

Defendants’ argument that the interference WPEngine alleges consists of acts they’d a proper to take fares no higher.”

B. Irreparable Hurt

Mullenweg and Automattic fully failed at defending in opposition to WP Engine’s claims of irreparable hurt if the injunction isn’t granted. The choose wrote:

“Defendants counter with 4 arguments. None is persuasive”

C. Steadiness of Equities

On this a part of the ruling the choose needed to weigh the influence of the injunction on each events. The choose discovered that WP Engine had good cause for acquiring an injunction to stop additional hurt and that there can be no influence on Automattic or Mullenweg.

The choose wrote:

“The conduct described at size above – together with the termination of WPEngine’s entry to WordPress, the interference with the ACF plugin, and the extra burdens imposed on WPEngine’s clients, such because the sign-in pledge – demonstrates that WPEngine has a big curiosity in acquiring preliminary injunctive aid.

Defendants’ arguments in opposition don’t set up that they are going to endure any harm that overrides WPEngine’s curiosity in acquiring aid. …Requiring Defendants to revive entry on these phrases whereas this motion proceeds imposes a minimal burden.”

D. Public Curiosity

This a part of the ruling addresses how granting the injunction impacts events past the plaintiff and defendants. The choose concluded that denying the preliminary injunction would trigger important hurt.

The courtroom defined:

“Right here, the general public penalties of withholding injunctive aid are important. Mullenweg himself acknowledges that ‘[t]oday, greater than 40% of all web sites run on WordPress.’

…Over two million web sites run the ACF plugin Mullenweg allegedly tampered with, and people customers depend on the steadiness of the plugin, and WordPress extra broadly, to function their web sites, run their companies, and go about their day on-line.

Furthermore, the provision of WordPress as open-source software program has created a sector for corporations to function at a revenue. This contains Mullenweg’s personal corporations like Automattic and Pressable, and as Mullenweg himself acknowledged in 2017, it additionally contains WPEngine, which on the time, Mullenweg described as ‘the biggest devoted managed WP host…’

Those that have relied on the WordPress’s stability, and the continuity of help from for-fee service suppliers who’ve constructed companies round WordPress, shouldn’t need to endure the uncertainty, losses, and elevated prices of doing enterprise attendant to the events’ present dispute.

Defendants’ arguments in opposition don’t persuade in any other case.

…Accordingly, the ultimate Winter factor – the general public curiosity – weighs in favor of granting preliminary injunctive aid.”

E. Bond

Automattic and Mullenweg argued that WP Engine must be required file a bond of $1.6 million to make sure that they’re compensated for potential prices and damages if it’s later discovered that the preliminary injunction was granted with out enough foundation.

The choose agreed with WP Engine’s argument that reverting to the established order, to how issues had been on September twentieth, would don’t have any impact.

They wrote:

“WPEngine’s arguments are persuasive. …the Court docket finds that any hurt to Defendants ensuing from the issuance of preliminary injunctive aid is unlikely, because it merely requires them to revert to enterprise as normal as of September 20, 2024. Accordingly, the Court docket declines to require WPEngine to publish a bond.”

F. Scope Of Injunction

The courtroom has ordered the defendants, their coworkers, and anybody serving to them to cease doing the next issues:

  • Stopping WP Engine, its workers, customers, clients, or companions from accessing WordPress.org.
  • Disrupting WP Engine’s management over or entry to plugins or extensions hosted on WordPress.org
  • Modifying WP Engine plugins on WordPress installations (web sites constructed with WordPress software program) by unauthorized auto-migrate or auto-update instructions
  • The courtroom ordered that the defendants take actions inside 72 hours to deal with WP Engine’s claims and restore issues to the way in which they had been on September 20, 2024.
  • Delete the checklist of WP Engine clients from the WP Engine Tracker web site and the GitHub repository.
  • Restore WP Engine worker login credentials to WordPress.org and login.wordpress.org.
  • Disable any “technological blocking” like IP blocking, that had been arrange round September 25, 2024.
  • Take away the checkbox added on October 8, 2024, at login.wordpress.org, which required customers to substantiate they had been ‘not affiliated with WP Engine in any approach, financially or in any other case.’
  • Restore WP Engine’s management over its Superior Customized Fields (ACF) plugin listing itemizing to the way in which it was on September 20, 2024.

The injunction goes into impact instantly and can stay till the courtroom points a closing judgment after the trial.

A Win For WP Engine And The WordPress Neighborhood

Many individuals agree with the precept that those that revenue from WordPress ought to give again to it. Nevertheless the overwhelming sentiment on social media has not been supportive of how Mullenweg’s actions in opposition to WP Engine. At the moment a choose agreed with WP Engine and issued a preliminary injunction of their favor.

Featured Picture by Shutterstock/Brian A Jackson


#Decide #Sides #Engine #Automattic #Mullenweg #WordPress #Dispute


Search Engine Journal


#Decide #Sides #Engine #Automattic #Mullenweg #WordPress #Dispute


Roger Montti , 2024-12-11 08:01:00

Bheir Togail Automattic AI gu WordPress

Dh’ainmich Automattic gun deach WPAI fhaighinn, companaidh a chruthaicheas comasan le cumhachd AI a nì WordPress nas fhasa agus nas èifeachdaiche a chleachdadh. Bidh prìomh theicneòlasan nan aplacaidean gnàthach air am filleadh a-steach do thabhartasan ùra le Automattic.

WPAI

Sgaoil WPAI a’ chiad toradh aige, CodeWP ann an 2022. B’ e àrainneachd leasachaidh amalaichte AI (IDE) a bh’ ann an CodeWP do luchd-leasachaidh, a’ toirt cothrom dhaibh còd a ghineadh gu sgiobalta a tha air a bharrrachadh airson coileanadh agus inbhean WordPress.

Is e an dàrna app a rinn WPAI AgentWP, a chaidh fhoillseachadh san Lùnastal 2024. Bha AgentWP na àidseant AI fèin-riaghailteach a dh’ fhaodadh a dhol an gnìomh gu for-ghnìomhach leithid atharrachaidhean dealbhaidh a dhèanamh. Bidh e a’ clàr-amais làrach-lìn agus comasach air sruth-obrach làrach-lìn WordPress a leasachadh bho ghineadh susbaint gu còd.

Bidh teicneòlas an dà aplacaid air fhilleadh a-steach do WordPress.

A rèir fios bho WPAI:

“Tha sinn air bhioran feachdan a chur còmhla le Automattic gus crìochan a phutadh air mar as urrainn dhuinn inntleachd fuadain a chuir an sàs gus barrachd buaidh a thoirt air an CMS a bheir cumhachd don mhòr-chuid den eadar-lìn,” arsa Seumas LePage. “Le bhith ag amalachadh ar teicneòlas agus ar rannsachadh le toraidhean Automattic an-dràsta agus san àm ri teachd, bidh e comasach dhuinn luathachadh a dh’ ionnsaigh ar n-amas gus WordPress, Siostam Obrachaidh an Lìon, a dhèanamh nas ruigsinneach don h-uile duine. ”

Automattic a ‘mìneachadh:

“Is e companaidh tòiseachaidh AI a th’ ann an WPAI, le fòcas air fuasglaidhean AI a thogail airson WordPress. Bidh an sgioba stèidheachaidh sgoinneil air a chùlaibh – Seumas LePage, Greg Hunt, agus Ovidiu “Ovi” Iulian Galatan – a’ tighinn còmhla ri Automattic gus sgrùdadh AI gnìomhaichte a stiùireadh mar phàtran eadar-obrachaidh airson WordPress. Bidh iad ag obair air deuchainn, togail, agus amalachadh fhuasglaidhean AI ùr-ghnàthach a-steach don phrìomh eag-shiostam gus ath-mhìneachadh a dhèanamh air mar a bhios luchd-cleachdaidh agus luchd-leasachaidh ag obair le WordPress.”

Leugh an sanas air Automattic:

Automattic a’ cur fàilte air WPAI

Leugh an sanas air WPAI:

Tha WPAI air fhaighinn le Automattic

Thoir sùil air an inneal WP Chat an-asgaidh aig WPAI a fhreagras ceistean co-cheangailte ri WordPress (fhad ‘s a tha e fhathast ri fhaighinn):

https://wp.chat

Ìomhaigh sònraichte le Shutterstock/Shutterstock AI


#Bheir #Togail #Automattic #WordPress


Search Engine Journal


#Bheir #Togail #Automattic #WordPress


Roger Montti , 2024-12-10 20:56:00