The problem is with your selectors: attributes: { content: { type: ‘string’, source: ‘html’, selector: ‘p’, }, content2:{ type: ‘string’, source: ‘html’, selector: ‘p’, }, }, You’re only using p for both attributes. When the block looks at the saved HTML to validate it, it checks to see if the value of the selectors matches … Read more
When we register a block type we define how the block structure should be in the moment it is added to the editor. After the block type is added to the editor we have an actual block. The initial template prop in the InnerBlock defines which innerBlocks should be added when adding the (root) block … Read more
The only way to do this at the moment is by using the renderAppenderprop onInnerBlocks. This prop is only available in the Gutenberg plugin until WordPress 5.3 is released. The theory would be to use state in each CustomCard to track if there has been a block added, then return false from the renderAppender function … Read more
The code from the docs is JavaScript. You have to set up Webpack and build this type of JS. So, you could use something like Create-Guten-Block to set up that build process, and then replace the contents of “block.js” with that JS from the docs. (I sure wish they would improve the docs to make … Read more
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.
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
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
You can define a getEditWrapperProps function when you register the block, and return an object that sets the props for the wrapper. The function will be passed the props for the block, in case those are needed. registerBlockType( ‘wpse/example-get-edit-wrapper-props’, { title : ‘getEditWrapperProps() Example’, // … getEditWrapperProps( props ) { return { ‘data-foo’: ‘bar’, ‘data-quix’: … Read more
Bottom border (HR) can be removed using CSS: #__BLOCK_ID__.postbox:not(.closed) .postbox-header{ border-bottom: none; } p.s. change __BLOCK_ID__ to first parameter used in add_meta_box() function.