Ideally, yes. Blocks are supposed to be WYSIWYG. See the Editor Styles section of the Gutenberg Handbook for how to load theme styles in the editor. You need to add an editor stylesheet with add_editor_style(), the same way you did with the previous editor, but to support the block editor you need to declare theme … Read more
I figured out that I was passing the wrong information to the attributes. I changed it to this and it started working: attributes: { mediaID: { type: ‘number’, }, mediaURL: { type: ‘string’, source: ‘attribute’, selector: ‘a’, attribute: ‘href’, }, },
The problem you are facing is probably that the div (or a parent) gets re-rendered when a change is made in the DOM tree and the handler you assigned to it no longer works. This is because the element you see after the re-render is actually a new one which doesn’t have the handler assigned. … Read more
Creator of create-guten-block here. You should be building Gutenberg blocks via companion plugins. Keep your theme for styles only 🙂 That’s the best practice for now.
As Milo noticed, shortcodes should return content instead of echoing it. So change while($query1->have_posts()) : $query1->the_post(); echo ‘<div class=”menu-thumb”>’; the_post_thumbnail( ); echo ‘</div>’; echo ‘<div class=”menu-title”>’; the_title( ); echo ‘</div>’; echo ‘<div class=”menu-content”>’; the_content( ); echo ‘</div>’; endwhile; to while($query1->have_posts()) : $query1->the_post(); $div = ‘<div class=”menu-thumb”>’; $div .= get_the_post_thumbnail( ); $div .= ‘</div>’; $div .= … Read more
It isn’t documented but if we take a look to the gallery block, we see it passes an extra prop to the MediaUpload component. Try to pass gallery as well as multiple to the component.
FWIW, there was an error in the wp_enqueue_style function I received. This one works fine: // Enqueue optional editor only styles wp_enqueue_style( ‘pbdsblocks-blocks-editor-css’, plugins_url( $editorStylePath, __FILE__), [ ], filemtime( plugin_dir_path( __FILE__ ) . $editorStylePath ) ); Note the third argument has changed to [ ] from [‘wp-blocks’]
You are creating the MySelectControl component but it is not being used inside the edit function/component. Include it there and it should appear. If you want it to appear in the settings sidebar, rather than in the editor, simply wrap the component inside the inspector-controls component (from the package @wordpress/editor): <InspectorControls> <MySelectControl /> </InspectorControls>
You can save your data into the database by using save method in registerBlockType. Just make requests on ComponentDidMount via using JS fetch API, store and use it in edit method. In the end use save method instead of using Server Side Rendering. Server side rendering should only be use if your content changes like … Read more
SHORT VERSION Using css it’s possible to use of the :not() selector to exclude Tinymce instances, e.g. body:not(.mce-content-body) {…} LONG VERSION Let’s assume we have declared theme support for editor styles and included an editor stylesheet somewhere in our theme (e.g functions.php) like this: add_theme_support( ‘editor-styles’ ); add_editor_style( ‘something/something/css/editor.css’ ); For the sake of this … Read more