That label is a translatable text and its translation is retrieved using wp.i18n.__(), so you can change the text like you could in PHP via the gettext filter, except that in JS/Gutenberg, you’d use i18n.gettext. Working example: // Define our filter callback. function myPluginGettextFilter( translation, text, domain ) { if ( text === ‘Write an … Read more
You don’t. That’s not how block attributes work, and it’s not what they’re for. A blocks attributes belong to that block, and are used by the editor to generate that blocks HTML, but once they’re saved in the database, they’re just HTML. There’s no block table, no mapping/index of block attributes in the database, post … Read more
Have a look at the handbook. And you’re right, put the code to distribute there. I’m quoting the handbook: SVN and the Plugin Directory are a release repository. Unlike Git, you shouldn’t commit every small change, as doing so can degrade performance. Please only push finished changes to your SVN repository.
No, you can’t have multiple InnerBlocks. But you can create a second intermediate block, just like WordPress Core does with the columns and column block.
I think I’ve figured this out. Instead of creating a block variation, I just created a brand new block using a block template. import { registerBlockType } from “@wordpress/blocks”; import { useBlockProps, InnerBlocks } from “@wordpress/block-editor”; const BLOCKS_TEMPLATE = [ [“core/heading”, { level: 2, placeholder: “Heading” }], [“core/gallery”, {}], ]; registerBlockType(“logo-grid”, { apiVersion: 2, title: … Read more
No, this is not possible with the current implementation of the format library and FormatToolbar component. Formats have no order other than the order they are registered in, and this cannot be changed once set, or influenced in core formats. Notice here the format toolbar component being added to the inline toolbar control slot: // … Read more
You may now retrieve the index of a inner block via the core/block-editor data module. You may pair it with the useSelect hook to keep the indexes up to date on changes. Something like this. Intentionally verbose for clarity. import {useSelect} from ‘@wordpress/data’; const Answer = ( blockProps ) => { const {index} = useSelect( … Read more
You don’t, rather the approach taken is incorrect, and this particular situation is not fixable. The group blocks anchor attribute for the ID is stored in the markup itself not the HTML comment, so by introducing an ID at the top level you are changing its value. Once this is done, the output of the … Read more
Maybe you will find this snippet helpful. I’m still searching for a better way to do this but as far as I can tell blocks are not aware of their own deletion. Instead we have to monitor the blocks from above. If you have a parent block type that has children, you can subscribe to … Read more
I’ve managed to pull and get it to run as I would expect. $ npm run start:random-game > [email protected] start:random-game C:\Users\…\game-review-block > wp-scripts start blocks/random-game/src/index.js –output-path=blocks/random-game/build/ <i> [LiveReloadPlugin] Live Reload listening on port 35729 asset index.js 25.4 KiB [emitted] (name: index) 1 related asset asset style-index.css 858 bytes [emitted] (name: style-index) (id hint: style) 1 … Read more