Note to self, rest-up and re-read the docs. So it turns out that the answer is written in the docs, but rather obscurely. If you check out the Frontend Enqueueing section of the Block Editor Handbook, you’ll see this statement. Frontend Enqueueing #Frontend Enqueueing Starting in the WordPress 5.8 release, it is possible to instruct … Read more
I was able to get there by doing the following. import * as wpDate from “@wordpress/date”; You can find the very limited documentation on that here: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-date/ I was able to use the following: const post = wp.data.select(“core/editor”).getCurrentPost(); const postDate = wpDate.format(“d|m|Y”, post.date); Then, when I needed it: <div> <RichText className=”snug huge” placeholder=”Your title here” … Read more
EDIT I just realized you’re doing this on the PHP side. There is a class called WP_Block_Type_Registry that you can use to see what is already registered: $registry = WP_Block_Type_Registry::get_instance(); if ( ! $registry->get_registered( ‘foo/column’ ) ) { // YOUR CODE } Gutenberg should fire a console error if a block has already been registered. … Read more
I could solve it with the function getColorObjectByColorValue (take a look at the gutenberg files). If you have something like const backgroundColors = [ { name: ‘Light Green’, slug: ‘light-green’, color: ‘#E6F0F0’ }, { name: ‘Light Gray’, slug: ‘light-gray’, color: ‘#F7F7F7’ } ]; then you can get the color name by const test = getColorObjectByColorValue(backgroundColors, … Read more
The reason it does not show up automatically is because it requires REST enabled to display. By default, show_in_rest is set to false when registering taxonomies and post types. There’s currently a Trac Ticket #42785 open to change this default functionality. So in short when registering a taxonomy while using the Block Editor you’ll need … Read more
This is a react related issue, so I suggest you take a look at Components and Props. In this case the edit function passes an argument, which is an object, and we can call props: registerBlockType(“my-plugin/my-block”, { //… edit: props => { return <MyComponent {…props} />; } }); This way of spreading would be the … Read more
When you register a custom taxonomy make sure to set show_in_rest to true. This way the taxonomy will show in the REST API which is what Gutenberg uses to get the data. Then you can use the selector: wp.data.select(“core/editor”).getCurrentPostAttribute(“my_taxonomy”);
You can accomplish this with the good ol’ wp_localize_script. Step 1: When you register your blocks script, you already will do something like this: wp_register_script( ‘my-awesome-block’, plugins_url(‘/blocks/dist/blocks.build.js’, __FILE__), array(‘wp-blocks’, ‘wp-element’,’wp-editor’,’wp-components’,’lodash’), filemtime(plugin_dir_path(__FILE__).’blocks/dist/blocks.build.js’) ); After this (within the same function) insert: //Do whatever to parse the json-file or get the categories, get them into a nice array … Read more
This is… nothing that can be answered in a few sentences. I will try to help. 1.: Make yourself comfortable with the way blocks are built, especially using node and webpack. I found a pretty good tutorial here: https://css-tricks.com/learning-gutenberg-1-series-intro/ 2.: Write down what kind of additional controls outside of the Embed URL you want to … Read more
You can (at the moment) not use InnerBlocks more than once within a block. However, you can bypass this by using a template for your InnerBlocks that contain Blocks which support InnerBlocks instead, like the core/column block. Like this: wp.element.createElement(InnerBlocks, { template: [[‘core/column’,{},[[‘core/paragraph’,{‘placeholder’:’Inhalt linke Spalte’}]]],[‘core/column’,{},[[‘core/paragraph’,{‘placeholder’:’Inhalt rechte Spalte’}]]]], templateLock: “all”, allowedBlocks: [‘core/column’]}); Some time ago, i … Read more