select the entire ‘buttons’ block once the entire buttons block is selected, For future reference, the wordpress.com button article is usually current although it is currently out of date at the moment.
Just figured out the solution: use ‘level’ => 3 as parameter. register_post_type(‘custom-post’, array( // […] ‘template’ => array( array( ‘core/heading’, array( ‘level’ => 3 ‘placeholder’ => ‘this is a H3’ ) ) ) ));
This took me a while to figure out… It’s a bug. The JavaScript error occurs because the onFilterValueChange function is not defined… Even though the WordPress documentation says this function is optional. Simply adding onFilterValueChange with an anonymous function removes the JavaScript error. E.g. <ComboboxControl label=”Font Size” value=”small” options={[ { value: “small”, label: “Small” }, … Read more
The short answer here is no. Widgets are written in PHP and blocks are written in JavaScript. Beyond that there pretty fundamental differences between the two paradigms in the sense of where they are stored, markup output approaches etc. You could take the approach of a dynamic block where the block is rendered on the … Read more
None of Gutenberg’s data stores expose selectors for this purpose yet, to the best of my knowledge. If any did, I would have expected to find it on core. If and when the Gutenberg experience expands to the plugin management screen I reckon we’ll see such a thing implemented. For the time being, if the … Read more
I think you can do this in a couple of different ways. I can’t help with the specific processing you want done (since I don’t know exactly what all you want done) but hopefully this gets you started. Option 1 Loop through all blocks and “process” each block independently. import { useSelect } from ‘@wordpress/data’; … Read more
I’ve updated this answer with more than one way to accomplish this. Though maybe it could go without saying the context of these is using the @wordpress/scripts package for development. Single bundle for all blocks This setup is most suitable for building some combination of blocks that have parent/child relationships (like Columns/Column) and thus one … Read more
core/buttons is a container block, it’s not the actual buttons. Instead, core/buttons contains core/button blocks. The same way that a core/columns block contians core/column blocks. You need to add core/button to your allowed blocks list.
One can use the built-in has_block( $block_type, $post ) function to check for specific blocks. The first input argument is the block type in <!– wp:{$block_type} –> and the second one is the post object. To find the corresponding block type, we can view it in the Code Editor view via the shortcut: Ctrl + … Read more
Yep, you just need to add ‘show_in_rest’ => true Here’s the full snippet: // Register Custom Post Type function custom_post_type() { $labels = array( ‘name’ => _x( ‘Post Types’, ‘Post Type General Name’, ‘text_domain’ ), ‘singular_name’ => _x( ‘Post Type’, ‘Post Type Singular Name’, ‘text_domain’ ), ‘menu_name’ => __( ‘Post Types’, ‘text_domain’ ), ‘name_admin_bar’ => … Read more