Nice update but some issues
-
There are a number of issues.
If you have third party plugins installed, like Toolset, that put extra buttons into the toolbar, on the Classic Paragraph block these appear also off the top left of the block. They display regularly in the Classic block.
Putting the classic block into a third party block such as Kadence columns triggers a broken block after going back into edit. Using regular paragraph blocks avoid this error.
It took me a while to figure out how to configure TinyMCE Advance and which blocks to put blocks where, so ok for me but I can see people getting frustrated with the block editor, especially when they mix with third party block solutions.
In the settings for TinyMCE you have a misspelling in the Append all buttons to the Top Toolbar in the Classic and Classic Paragraph Blocks description. You spelled fourth -> forth.
Despite the above I do like what you have done.
-
Thanks Andrew.
That sorted all the issues in my opening post, even putting the blocks into the various column options. Great work.
I like the way you can transform from classic block to classic paragraph to paragraph and back again and combine blocks back to one classic block again.
A number of things.
I notice that when I create a new post, a classic paragraph gets added automatically. Perhaps some settings to set what happens by default, Classic Block, Classic Paragraph or user defined ( none with option to add other types of blocks). I notice if you try to remove the initial classic paragraph, a new one is added again, straight away. And the + to the left stops working after deleting/re-appearance of the classic paragraph. Switching it to a classic block, doing a add a different block type, then delete the classic block, dance is the current workaround.
Generally when you add a Classic paragraph there is no + icons underneath
to add other types of blocks.Similarly when you add columns, a classic paragraph gets automatically added. Users might want to add a different type of block. There is a few workarounds like converting deleting but these are a bit cumbersome with the wack-a-mole nature of Gutenberg.
Not sure if the following is a feature but in the process of fiddling with blocks and what I think was a kadence block row with two columns, then viewing and going back to edit, fixing/resolving a breakage by converting to classic block, I ended up with that classic block with two paragraphs in two columns. Checking the html isee it wrapped in some classed divs
<div class=”wp-block-columns has-2-columns”>
<div class=”wp-block-column”>
<p data-tadv-p=”keep”>content</p>
</div>
<p data-tadv-p=”keep”></p>
<div class=”wp-block-column”>
<p data-tadv-p=”keep”>Content</p>
</div>
</div>It actually looks quite nice but I cannot reproduce this? The only thing I can think of is that it’s part of the new block editors resolve mechanism.
Thanks for the review š
I notice that when I create a new post, a classic paragraph gets added automatically.
Right. This is because the classic parafraph is set as default block. It only works for the first block when starting a post, or after adding a “parent block” like columns.
Currently a plugin cannot control how that works in different contexts. I’m considering to add checkboxes for both classic and classic paragraph blocks but plugin’s settings screen will get pretty close to “wall of checkboxes”… Will probably have to think about some other way or at least some better UI for such “very very advanced” settings š
Generally when you add a Classic paragraph there is no + icons underneath to add other types of blocks.
I can see the icon. It’s higher on the left (assuming that’s because of the TinyMCE toolbars). However clicking it works only the first time (sometimes). The same happens for the classic block, but the other default blocks seem to work. Think this is a Gutenberg big.
Yeah, the workarounds are cumbersome. Will keep looking in ways to fix this (in the plugin or in Gutenberg).
I ended up with that classic block with two paragraphs in two columns. Checking the html isee it wrapped in some classed divs
This is a “feature” š When you convert from any block to the classic paragraph block, it takes the previous block’s HTML output as content. That way you can continue editing with TinyMCE. Looked at how to best handle these conversions, but that way seems the most logical/expected.
(The
data-tadv-p="keep"are from the plugin. It’s a crude way to always keep the<p>tags… These will be stripped on saving the post.)
The topic ‘Nice update but some issues’ is closed to new replies.
