Jody2879

@arniepalmer @rizaardiyanto Can't someone with admin permissions, which are usually required to access a file manager, install any dangerous plugin themselves?

Worst decision ever to allow a plugin to access your web server. It is not necessarily about the file manager plugins, its about the others that get cracked, authorise a bad actor and boom! Your server is cracked. The ONLY sites that I have had to fix through a hack were hacked this way. Do not install a file manager plugin, is my best advice.

File Manager plugin in WordPress feels clunky and old. So I'm creating a new File Manager plugin that feels modern and fresh..

@groundworxdev It's about general trade-offs, not specific examples. Blocks add infrastructure for editor flexibility that many projects don't need. They make debugging harder and introduce more moving parts than simple templates. The complexity benefits the paradigm, not the client.

Unless you provide a specific case with a clear example, I’m not sure there’s much to discuss here. I’ve asked a few times for concrete scenarios where blocks create problems the old stack solves better. So far it’s been abstractions about complexity and distributed logic without actual examples. If you’ve got a real use case in mind, I’d genuinely like to understand it. Otherwise we’re just talking in circles.

Seeing WordPress developers dismiss block-based development while defending the old stack as “real development.” You know the stack: ACF, PHP templates, global CSS, global JS, everything hardcoded in the theme. Here’s the thing, that approach was fine when that’s how WordPress was built. But WordPress fundamentally changed. Now it’s structured, modular blocks with self-contained JS and CSS that fall back to your theme settings. It’s actually beautiful. Clean. Maintainable. Scoped instead of global chaos. But a lot of developers built entire businesses on the old approach. They’re fast at it. Profitable from it. Their expertise is valuable because of it. The new paradigm threatens all of that. If they admit modern WordPress is better, they have to admit their stack is outdated. Their expertise needs rebuilding. Their business model needs rethinking. So instead of learning, they undermine it. “Real developers code properly.” “Dragging blocks isn’t development.” Agencies should be reevaluating this. Gutenberg-native development is easier to maintain, easier to edit, faster to build new themes. Better accessibility support built in. Yes, there’s upfront cost to transition, but once the structure is in place, everything moves faster. You stop spending energy sustaining the old stack and start innovating on better experiences for clients and users. Embrace it, don’t fight it. #WordPress #WebDevelopment #TechThoughts

@groundworxdev Markup quality matters, but that’s not the issue here. Blocks distribute behavior across editor state, config, and templates. As you add conditional logic and shared components, the complexity compounds, much of it to support editor‑driven flexibility many projects don’t use.

You’re still being pretty vague though. Blocks become the functional aspect, paired with theming, paired with custom field options for UX and editing control. Use semantic HTML elements and you get solid theme.json support. Add color and typography controls, extend element-level settings if needed. The less you replace real HTML elements with divs and spans enforcing hardcoded classes, the easier everything becomes. Cleaner markup, better accessibility, easier to maintain. You can also have settings only in the editor and render server-side in PHP if you want that control and reviewability. The “serialization spreads logic around” concern goes away when you’re building with proper semantic structure instead of fighting it. What specific use case are you thinking of where this approach fails?

@groundworxdev Mainly reviewability and predictability. Blocks serialize a lot, spread logic around, and can change behavior as the editor evolves. That’s fine for some sites, painful for others.

I’m not assuming motives, I’m observing patterns. WordPress core moved to blocks. That’s platform direction, not opinion. You mention “real trade-offs” and “engineering decisions”, what specifically are they? I’m genuinely asking. Because from what I’ve seen, the modern stack is cleaner, more maintainable, and faster once you make the transition. If there are technical reasons to prefer a different approach, I’d like to hear them.

@jamesckemp Flexibility, and too big to fail.

Why do you choose WooCommerce?

@jamesbrooksco @Inoreader

I know this is a RIDICULOUS question - but how do y'all subscribe to blogs these days? Like...feed readers are not really a thing anymore, right?

@gregg_tweets @nickmdiego I sometimes believe that I am the only one who does that.

@nickmdiego Live staging subdomain at destination server.

Calling all WordPress developers. What's your primary local WordPress development tool? If Other, please note what tool you're using in the comments. Also interested in your favorite features of each.

@briancoords Call him Casio.

Our family is divided on naming this guy. Please vote in the poll (see reply below) and help restore the peace.

@xaver_ @KatieKeithBarn2 As a customer and developer, I might be forgiving of this approach for products I use and like. However, these marketing tactics tend to push people away emotionally rather than bring them closer.

@Jody2879 @KatieKeithBarn2 Adobe does this for years and you are free to do it with all your subscriptions. I think this step gives some buyers the option to stay. If you really need/like the product you shouldn’t care about some %. It helps developers which helps you with a better product.

We've implemented a new flow for cancelling a plugin subscription, aimed at explaining the genuine reasons for keeping your plan active without misleading or confusing the customer. 4 clicks in total. Do you think this is a good balance?

@KatieKeithBarn2 I mean hypothetically - I'm not actually a customer.

@KatieKeithBarn2 After seeing that there's a better price hidden in the cancellation process ('special offer'), I'd probably test the cancellation flow with every other plugin I have from your company. As a customer, this makes me feel a bit betrayed about the prices I've been paying.

@KatieKeithBarn2 For me, the best approach is to have a laptop right next to the bed and start working right there.

What are your tips for getting out of bed in the morning? For the last 10 years, the school run forced me to get up at a certain time. However, my daughter just switched to online school and now I'm having daily lie-ins, procrastinating on my phone instead of working 🛌

@bretwp detachment from self

@Jody2879 What helps?

Have you considered just holding yourself accountable for your actions?

@magicroundabout @TurboAdmn My pleasure! Hope you'll keep it running for a long time. I'd be happy to pay for an upgrade as you keep adding new features.

@TurboAdmn is a brilliant command UI for WordPress. No need to install plugins on each site, just instant navigation anywhere. Clean, fast, and really well thought out.

@magicroundabout Great post! Thanks for that. I was really curious what you think about this launch and specifically searched for your opinion on it.

@schutzsmith Making the repository configurable via wp-config seems inevitable - Matt can hardly object given his stance. WP Engine's alternative solution could turn this into their biggest community win yet, completely backfiring on any attempts to eliminate them.

Don’t get me wrong, I LOVED WordPress but we were sold a bag of lies. It’s disheartening but a professional in those spaces can no longer ethically recommend it as a solution that is stable.

@ryantownley You don't have to wait: turbo-admin.com

Well, this is a no-brainer. Instantly search, navigate, install plugins, etc. on your #WordPress site from a command bar available when logged into admin. Can't wait to try it out. Check out CommandUI! commandui.com/?r=ikiKtpn0td4