You can use do_blocks and insert block content as string in that function, which will like do_shortcode transform block’s html and metadata in html comments into final html. I am not sure if it works for reusable blocks, I never used them. If you want to use block theme, you should develop your own blocks … Read more
Gutenberg block HTML image rendering override
Gutenberg block not displaying prop values
Different blocks work differently. Some blocks are just a comment, while some require HTML. Others depend on inner blocks for their actual content. The Social Links block is a wrapper block and each social link is a variation of the Social Link block. But no matter how the block actually works, the easiest way to … Read more
I found it – it is dynamically injected as entity in gutenberg/packages/core-data/src/index.js, on line 22 const entitySelectors = rootEntitiesConfig.reduce( ( result, entity ) => { const { kind, name } = entity; result[ getMethodName( kind, name ) ] = ( state, key, query ) => selectors.getEntityRecord( state, kind, name, key, query ); result[ getMethodName( kind, … Read more
As far as I can tell from looking into block editor store (you can use Redux devtools plugin for browser for that), entity for reading options is not registered. That means you cannot use getEntityRecord selector, which is usual way to obtain such data. Instead, either you can: Use apiFetch to fetch data from designated … Read more
How can I add a custom button to the post editor?
Unfortunately, there is no easy solution. You could use editor.BlockEdit hook to change default core/image Edit component, and copy the code from current trunk version, and change there to not use MediaPlaceholder, but MediaUpload wrapped in MediaUploadCheck. However, that would create problem that all core/image blocks would be changed and it would not be futureproof, … Read more
Rather than passing handleChange directly to onChange, you can use an anonymous function to call it: <CheckboxControl key={index} checked={isChecked} label={element.title} help={element.description} name={element.name} onChange={(value) => { handleChange(element.name, value); }} /> Then your handleChange function can accept the name and value as its parameters. const handleChange = (name, value) => { setInputs(values => ({…values, [name]: value})); };
By wrapping everything in a <SlotFillProvider> and rendering MyTestFill it works, here is the code: const { Fill, Slot } = createSlotFill( ‘MyFill’ ); const TestFill = () => <Fill>My item in the editor</Fill>; export default function Edit() { return ( <p { …useBlockProps() }> <SlotFillProvider> <Slot /> { __( ‘Fill Test – hello from … Read more