#fuck wordpress

[emeraldoo]

holy shit i just got such a good idea (in theory)

ok so remember how tumblr/wordpress is selling our data to midjourney and you have to manually opt out on all blogs+sideblogs

what if we made poison sideblogs that post the most rancid, dataset destroying, fetish unconcealed bullshit and opted into the midjorney horseshit

just saying it's like the nightshade/glaze stuff but way more accessible bc you dont need a mega computer

[worldstrangeweb]

Good news: Apparently Verizon is selling tumblr to Wordpress.

Bad news: they are going to keep the porn ban in place.

[inner-space-oddity]

I gotta lock in (except doing so requires me to build a site on WordPress Playground and I'd rather eat my own organs)

[ratfc]

Don't become web designers guys, it's not worth it

[thegardengrows-infrozenrain]

on mobile app, where the communities view is literally just a container for the mobile website...

...i guess there's a new fucking button now for their dumbshit new subscription.

right over post too, they're trying to get you to accidentally click it. (isn't that illegal?)

[ardathksheyna]

Yeah, I had to pop back in to drop some PHP dev snark.

My brain just imploded doing a code review on a WordPress plugin. Couldn't get through the review without sounding like Uncle Roger

PSA for WordPress devs. If you hook into a filter, make sure you're returning the first parameter of that filter so you're not blowing up a user's site. I just debugged an issue with a plugin that was hooking into the_content, but was returning a null instead of the first parameter, which resulted in missing content.

[ardathksheyna]

I'm a PHP Dev—and I fucking hate WordPress

Or, if you're going to implement a templating language, use Handlebars or Twig instead of trying to roll an inconsistent half-assed version using html comments and JSON strings.

Disclaimer: I normally try to avoid talking about work-stuff but there is just some shit that is seriously bugging me right now about WordPress.

WordPress' push towards full-site editing and block themes has been frustrating, to say the least. Lack of documentation being a huge part of that frustration, and changing features between major versions is another.

Then there's the little things like modifying a parameter in that embedded JSON string but the site editor isn't smart enough to look at that parameter and "go hey, I need these classes" and add them. Instead, it just throws an unexpected content error at you.

That issue right there throws the claim "oh you can still code these templates in an IDE or text editor like normal" out the window. Especially when the code inside the html comment is touchy about spacing, or the templates themselves don't have an opening/closing tag structure that makes sense.

The editor not being smart enough to recognize a parameter and add the needed classes was today's frustration. It's not a hard feature to implement—I know WP devs who have developed blocks that do it automatically. There is no reason in the world why WordPress can't do the same.

Finally, Gutenberg needs a serious UX audit. Settings are in the block tool-bar when they should also be included in the side bar is frustrating, to say the least. It's namely layout settings—like the Cover block, for instance. Vertical alignment settings for the content inside the block are actually on the block's tool-bar, but if you're looking for them in the side bar, they're not there. Either put them in both spots, or eliminate one of them if you can't be bothered to be consistent.

[luvm4rk]

this site is so dead