You’ll want to target the block specifically via javascript. Brief example: wp.domReady(function() { wp.blocks.unregisterBlockType( ‘coblocks/map’ ); }); Save that to a js file and enqueue it via your custom function: add_action(‘enqueue_block_editor_assets’, ‘your_custom_enqueue_fucntion’)
In this case it seems a block pattern might suffice. The Group block has a templateLock attribute which can be set to all to prevent any additional blocks from being inserted within and also keep the Heading and Paragraph blocks from being moved or deleted. Here’s an example with the template lock and a custom … Read more
This happens because the Component need the correct data type. Use “number” when getting the value. Use “String” as the attributes type. const onChangeValue = ( newValue ) => { setAttributes( { value: String(newValue)} ) } <RangeControl label=”Rating” value={ Number(attributes.value) } onChange={ onChangeValue } min={ 1 } max={ 10 } step={ 0.5 } />
It’s because you have multiline: true, as documented: By default, a line break will be inserted on Enter. If the editable field can contain multiple paragraphs, this property can be set to create new paragraphs on Enter.
No, you don’t, and for very good reasons that might not seem obvious at first. In essence your block needs to be available everywhere and to be able to handle that, even if it does this by not displaying anything. Just because you’re in the site editor doesn’t mean the block won’t appear inside a … Read more
In this case I think it would be easiest to simply ignore any Gutenberg-specific implementation and set up the button’s click event to click() the first linked image in the gallery listing. The following searches the page for “gallery buttons” and the first linked image in a gallery block, then sets up the buttons to … Read more
add_filter( ‘write_your_story’, function ( $string, $post ){ return ‘ ‘; }, 10,2); Also answered at: https://wordpress.org/support/topic/remove-type-to-choose-a-block-block-placeholder/ Docs: https://developer.wordpress.org/reference/hooks/write_your_story/
There is no impact on the loop in the current iteration. Gutenberg created content is just stored as HTML inside the post_content column of the database, and output with the_content(). Same as before. As for site-customisation, you said it: No-one knows precisely at this point. There are no technical details on how site-customisation will work … Read more
The block editor (formerly known as Gutenberg) is the default editor. You should not need to install the plugin or choose an option to make it the default. The plugin is now just for following and testing future developments, and the Settings > Writing option only appears if you’re using the Classic Editor plugin. The … Read more
only the JS file translation does not work It’s most likely because WordPress couldn’t find your translation file, which should be in a valid JED format, like so: { “domain”: “my-text-domain”, “locale_data”: { “my-text-domain”: { “”: { “domain”: “my-text-domain”, “plural-forms”: “n != 1”, “lang”: “en-us” }, “Shortcode Title”: [ “Shortcode Title translated” ], “Display it?”: … Read more