Matt Mullenweg and WordPress Hijack the Advanced Custom Fields Plugin – Pixel Envy
pxlnv.com
A bit of background, for those not steeped in the world of WordPress development: there exists a plugin called Advanced Custom Fields (ACF) which allows developers to create near-endless customization options for end clients in the standard page and post editor. It is hard to explain in a single paragraph — the WordPress.com guide is […]
  • schizo@forum.uncomfortable.businessEnglish
    261·
    16 days ago

    The really hilarious part is that he’s hijacking the link to ACF.

    The link that contains the ACF trademark, since WPEngine owns the trademark.

    So, the guy mad about trademark infringement is… busy hijacking links and committing trademark infringement?

    Good show, I’m sure his lawyers are VERY happy about this one.

    • MangoPenguin@lemmy.blahaj.zoneEnglish
      101·
      16 days ago

      People like this aren’t usually rational, they’ve just snapped for whatever reason and are doing whatever makes sense in their own head at the time.

  • catloaf@lemm.eeEnglish
    17·
    16 days ago

    Wordpress is seizing plugins now? Jesus, they really are speedrunning the enshittification pipeline.

    My personal site runs on Wordpress, and even though I’m not directly affected by this, I’m definitely moving off. I use other plugins, and for all I know, they might seize those ones tomorrow and start pushing changes.

      • catloaf@lemm.eeEnglish
        3·
        16 days ago

        No. My site is a semi-hosted instance (they have turnkey applications, but also give shell access and a lot of flexibility) so I’m going to see what they have for easy deployment first. A static page generator if nothing else looks useful.

        Honestly, there’s not much on the site, so I might just take it down entirely.

    • podperson@lemm.eeEnglish
      4·
      16 days ago

      Yep - I’ve done both volunteer/free and professional work with WordPress, but after all of this drama that Matt has caused, I’ll be abandoning the platform for all future work. Too much uncertainty that happened at the drop of a hat, due to one person’s actions. Cant justify ever recommending that to anyone and feel like I’m presenting a sustainable and supportable option. Bummer too, since for certain use cases, it checks a lot of boxes.