Відео

That's definitely something you could do if you were building out your custom settings panel by hand in JavaScript/React. You can sort of see how they're figuring out which variation is active in this code here, though it's a big messy: github.com/WordPress/gutenberg/blob/trunk/packages/block-library/src/group/variations.js

@@BrianCoords thank you!

Good to know that many of us are in the same place trying to figure out the same workflow issues.

Yep. I'm hoping to record some thoughts on some of the new features for block styles this week as well.

For sure performance is a legitimate concern, but these filters exist and are already executing on page load regardless. Core uses them pretty regularly, and that's not even considering the number of blocks that are dynamic, meaning built entirely from PHP, not stored statically inside the content. This is pretty normal in WordPress and the alternative (altering them before they're saved in the database) is much more likely to cause problems.

So the 'template' argument on register_post_type takes an array of blocks. You can pass it a pattern block or a synced pattern block. I'll just note that I did have some issues with a synced pattern block working correctly like this (especially when combining it with blocks that had bindings) gist.github.com/bacoords/4711fc205898e701eaba36137d71d476

ACF might be overkill for core - it's good plugin territory. But a UI for managing CPTs and basic Custom Fields from inside core would be amazing.

Nope, but that's the way WordPress core has always been. You can register a "metabox" but you've always had to write the actual HTML of it yourself. This is actually a step forward because in classic WordPress you had to write the logic to save the postmeta fields as well.

Yeah agreed, but I also really don't like the old drawer at the bottom of the block editor. There's some new UI coming that'll be a separate screen for this type of stuff, but I would love to be able to swap out the main canvas the way you can for "Code Editor" mode - like a way to jump into "Data Editor" mode that just shows custom fields, title, etc.

@@BrianCoords Yeah, definitely not at the bottom. I'm a fan of the ACF Blocks approach with the In-Page field editing experience where you can toggle between the view and the meta fields.

Yep - I'd love that to be the case for the entire content area, ability to toggle between 'content' view and 'data' view where I could edit meta info, title, category, etc with much more space.

Nice! Some powerful stuff on the way

@@BrianCoords Sweet, thanks Brain -- looking forward to it. =]

Agreed- and I bet ACF's going to support this as soon as possible, too. They've been working on Block Bindings as well.

Thanks!

Saw your issue and responded. Definitely an opportunity for better naming there.

Yes it's public! Share your thoughts and ideas, please.

It's definitely hard to make a recommendation without knowing your specific site. A lot of Woo sites just need a lot of plugins. If you can, make a staging copy of your site and play around with using the TT4 theme and see how close you can get to Elementor.

Yes! Here's a demo repo, I just haven't gotten around to making the video yet: github.com/bacoords/example-wp-settings

@@BrianCoords Thanks will check it out.

Me too; the transcript as well shows from previous

Thanks for the heads up! This is fixed.

Yep, that's how I feel.

Thanks!

Yeah I'm thinking I'll have instructions for that in the documentation, though I'm not sure I'll go so far as making a Composer package for it.

Thanks! Yeah maybe I can do a CMB2 vs ACF explainer.

Thanks Mark - I would love to discuss some use-cases for block custom fields with other developers testing the FSE waters if you have any.

@@BrianCoords We currently have a build taking place and therefore I may well be able to contribute to this discussion on use cases. Having thought about this again though, it seems as though this could be functionality something like ACF should add to their plugin - add fields to any block.

Yeah definitely. The one downside of ACF is that you're split between setting things up in their UI and then also writing code. I've been enjoying just sticking to code only.

@@BrianCoords I always use PHP to register fields and groups in ACF anyway so no change for me

Haha I know! I've been holding off since the new block styles features coming in 6.6 really cover much of the same territory and I'm trying to see where they're going with it.

Yeah but the PHP code method in ACF is not my favorite. And they also don't offer adding custom fields to core blocks, just to ACF Blocks.

Yeah it looks like most people don't just use Bricks, they also add these extra tools like Automatic.css on top of it. I'm sure we're all most efficient in whatever tool we use the most often.

What makes you say that grids are useless? I've done a lot of client work with Bricks and css grid is super simple to use, it's basically same as if you were writing CSS in any other tool only a bit faster

@@95beats46 Try dividing parent div to 9 factors and have 2 child with ratio 7:2. Please educate me if i am missing something here. And without a plugin or additional css.

@@amitjangra6454 I'm assumming you mean 9fr (9 columns) with the first child spanning 7 columns and the second child spanning 2 columns? Hero you go: make the parent container a grid > Add any gap size you'd like > In "Grid template columns" add: repeat(9, minmax(0, 1fr)) > now select the child, assuming it's a block or a div then look for "grid item options", it should be at the very top when you select the child element, and put "span 7" in the "grid columns" field of the first child and "span 2" for the second child. You should have what you asked with that. No acss or any other plugins needed, just knowledge of grid structure

That's great! I only recently learned the whole 'logging' aspect and now I use it all the time.

That's great! So happy it helped.

Thanks for watching!

Thanks! Let me know what you think.

Yep this really only scratches the surface. They have great documentation showing even more features: querymonitor.com/wordpress-debugging/how-to-use/

For queries, I recommend Ryan Welcher's Advanced Query Loop plugin - it just extends the core query loop with some extra controls. wordpress.org/plugins/advanced-query-loop/ For dynamic data like custom fields, there's still work in core getting everything ready there, but Advanced Custom Fields Pro is starting to support it: www.advancedcustomfields.com/blog/acf-chat-fridays-using-the-block-bindings-api/