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
This can be done using the blocks.getSaveElement filter as shown in the example below. I would STRONGLY caution that this has the potential for bad times. Core blocks are static blocks. This means that the output is saved to the database. If you want to remove these spans, you’ll need to basically redo all of … Read more
You can do this with the editor.BlockListBlock filter. More info here. This allows you to do something like the following: const withCustomAttributeClass = createHigherOrderComponent( ( BlockListBlock ) => { return ( props ) => { const { attributes } = props; const { yourCustomAttribute } = attributes; const class = yourCustomAttribute ? ‘my_custom_class’ : ”; … Read more
The documentation for that control does not exist at this time. Instructions have not been written yet. It is an experimental component. You need to use an appropriate control in your blocks Edit component. Note that these are very new components, their design will likely change, it should be considered experimental and unstable. There is … Read more
It’s slightly complicated. The default editor in WordPress is what’s properly called the “block editor”, but while this editor was being developed it was known as the “Gutenberg” project. The development on Gutenberg was done in the form of a plugin, which people could install for the purposes of testing and contributing. When WordPress 5.0 … 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
I’m getting a Promise with the post object inside when I do a console.log( mypost ) Yes, because apiFetch() indeed returns a Promise object, and apiFetch() doesn’t assign the response received from the server to the mypost constant, and the return value of your then() callback is also not going to be assigned to the … 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