Oh, oh good, WP also *auto updated* everyone on the plugin they seized with incompatible code and broke a good portion of sites in the process on a Saturday! This is all very good and normal.
-
Oh, oh good, WP also *auto updated* everyone on the plugin they seized with incompatible code and broke a good portion of sites in the process on a Saturday! This is all very good and normal.
-
@[email protected] oh, jesus. They didn't even "update" it properly? fucking A.
almost like seizing a piece of code away from the people who knew what they were doing and forcing it on everyone is a bad idea. -
@aud Yeah, I'm poking around in the source right now to see what they did but Trac's really hard to find the offending changesets.
It could just be for those using prepend/postpend or something else but something's afoot.
-
@[email protected] what a disaster.
-
@aud So yeah, they just ripped out a bunch of code for the pro features, renamed some things, and bizarrely removed an entire section of the changelog from August?
Methinks they missed something, but here's my source on the broken: https://news.ycombinator.com/item?id=41830709
Worth noting someone in the comments is confused as to the breakage.
-
@aud Oh, oh, also you'll note the change was SEMVER Minor. Which...is a choice.
-
@[email protected] ahaaaaaaa christ. Wow. minor. lmao. no big deal! Nothing to see here, etc.
-
Xandra Granade 🏳️⚧️replied to Asta [AMP] last edited by
-
Asta [AMP]replied to Xandra Granade 🏳️⚧️ last edited by
@[email protected] @[email protected] mannnn I feel like @[email protected] would have some major insight/thoughts into how this kind of thing could be avoided with future projects (that do not rely on a single, central, "blessed" source for software distribution)
