TextControl is from wp.components not wp.blocks. const { registerBlockType, RichText, AlignmentToolbar, BlockControls, InspectorControls, } = wp.blocks; const { TextControl } = wp.components; Changing that I was able to get your block to work fine instead of error in Gutenberg 2.2.0.
The block id is saved in the clientId field. It’s regenerated at each save of the post and is only available in props in the edit function. In order to use this field as unique id in the save function, it needs to be saved as attribute in the edit section. It will be then … Read more
<InspectorControls> <PanelBody title={ __( ‘Settings One’ ) }> </PanelBody> <PanelBody title={ __( ‘Settings Two’ ) }> </PanelBody> <PanelBody title={ __( ‘Settings Three’ ) > </PanelBody> </InspectorControls> If you insert multiple Panelbody like I did in above code. You will have multiple inspector controls with first one being ope by default. Change the panelbody accordingly to … Read more
Not tested. I just was browsing looking for something else. But I would try something like this: onReplace: function() { var myID = props.clientId; wp.data.dispatch(‘core/block-editor’).removeBlock(myID); }
Add additional classes to gutenberg .editor-styles-wrapper
Still no way to disable them from what I can see, but the CSS you gave didn’t do what I wanted, so I used this: .edit-post-post-preview-dropdown .components-menu-group:first-child { display: none; } This just keeps the ‘Preview in new tab’ option.
I think your onChange function needs to pass the value, like onChange={(value) => updateUrl(value)}
This is presently not offered as an extension point. The source for the post editor’s toolbar shows that these items are hard-coded, and do not offer any filters or Slotfills. Issue #16174 provides a feature request for such extension points.
I was able to solve this by wrapping the BlockEdit component in my own markup: <Fragment> <div className=”customClass”> <BlockEdit { …props }/> <div> <BlockControls> <Toolbar> <IconButton { …iconProps } /> </Toolbar> </BlockControls> </Fragment>
As of the end 2020, I have found that the best way to find attributes related to a core block is to inspect it with the react developer tools. Under the components tab, search for [BLOCK_NAME]Edit to find the editing component, where [BLOCK_NAME] is something like “Paragraph”, “Heading” or “Button”. Then on the right side … Read more