That’s not how blocks work in Gutenberg. Your block code runs entirely in the block editor, and returns 2 things: Components to display in the editor UI Components that when rendered produce HTML that gets saved to the database That second one is the key part here, the final product is just a string of … Read more
Whatever issues you had that caused a block to be “killed” after editing was entirely unrelated to the two different methods of writing the block that you have outlined. Building a custom block using the following method (https://github.com/WordPress/gutenberg-examples/blob/master/03-editable/block.js) of attributes with the –es5 flag appears to be more stable in terms of backwards compatibility. If … Read more
If you’re adding theme support for editor-color-palette then you need to add styles for those colours to your stylesheet. As documented: Themes are responsible for creating the classes that apply the colors in different contexts. Core blocks use “color” and “background-color” contexts. So to correctly apply “strong magenta” to all contexts of core blocks a … Read more
That would be because they’re using oEmbed, not a shortcode. You should use the function the_content() to render the content of a post, as it applies all the things required to make embeds, shortcodes, etc work properly. If for some reason that’s not an option, you can apply the content filter. <?php echo apply_filters( ‘the_content’, … Read more
Your edit function is just missing a [ and ], i.e. you forgot to actually return an array, like so: return ([ // add that [ <InspectorControls key=”lx-authors-block-setting” style={ { marginBottom:’40px’} }> … </InspectorControls>, <div className=”lx-authors-block wp-block” key=”container” style={{ backgroundColor: attributes.bgColor}}> … </div> ]); // and add that ] Or you could instead wrap the … Read more
A new day, and refreshed Google-fu powers provided the simple answer: The level attribute needs to be an integer, not a a string. [ ‘core/heading’, [ ‘level’ => 3, ‘placeholder’ => ‘Subheading’, ‘className’ => ‘block-subheader-directions has-blue-alt-color’, ], ]
WordPress 5.1.1 uses React 16.6.3. You can see this in the package.json file in the development version of WordPress on Trac: https://core.trac.wordpress.org/browser/tags/5.1.1/package.json?rev=44861 This has already been updated in trunk to 16.8.4, so the next major version of WordPress will use at least that version.
According to the gutenberg handbook you can use the blocks.registerBlockType filter which allows you to play around with the block settings. For most of the wp core blocks modifying the supports.align property works pretty well: wp.hooks.addFilter( ‘blocks.registerBlockType’, ‘my-theme/namespace’, function( settings, name ) { if ( name === ‘core/pullquote’ ) { return lodash.assign( {}, settings, { … Read more
Add a custom HTML block immediately before and after the elements you’d like to hyperlink as a unit, using the respective opening and closing tags. No need for a group block.
The attribute in question should have the type of “string” so that it would be rendered properly. attributes: { description: { type: “string”, } }