Inconveniences and problems that occurred when a post created with a text editor was converted to an editor with 【Switch to block editor】 of the Classic Editor plug-in [Note]

Inconveniences and problems that occurred when a post created with a text editor was converted to an editor with 【Switch to block editor】 of the Classic Editor plug-in [Note]

Thank you for visiting. This page is an English translation of the Japanese site [Knowledge Base] using Google Translate. Please understand that there are some points that are difficult to read, such as sentences and expressions.

Block editor (Gutenberg) adopted from WordPress version 5.0. If you are new to WordPress after 5.0, it’s okay because all the posts have already been created in the block editor, but has it been like me for a long time? Even if you are creating a site, or if you started with 5.0 or later, do you bother with “Classic Editor”? For those who have reverted to the old editor, I think that “posts” and fixed pages, like me, are a mixture of those created with both the old and new editors.

Of course, if you use the Classic Editor plugin etc., you can edit posts and fixed pages created with the old editor as they are with the old editor, so it is impossible to convert all posts and fixed pages one by one to the block editor. It is not necessary to do it, but it is unlikely that WordPress will lose Gutenberg and return to the old editor, so I would like to edit it with a block editor if possible.

This site was also first posted in 2013, and has been in operation since the days when there were no fragments such as Gutenberg in the first place. Not only the difference in the editor, but also the decorative plug-ins that are running only for past articles are enabled as they are. Thinking about someday, I finally lifted my weight and started to organize those plug-ins and make them block editors from the beginning of 2021. The number of articles exceeded 2000, which was a difficult task.

Basically, to change a post from the old editor to the new editor, if the Classic Editor plugin is enabled, open the edit screen as usual (for those created with the old editor, the edit screen of the old editor will be displayed. If you click “Switch to Block Editor” in the sidebar on the right side, all the content of the text will be converted into one block called “Classic Block”.

Of course, there is no problem with this as it is, but as it is, the features such as “managing each part with blocks (lumps)” and “easy to move blocks” unique to the block editor cannot be used at all, so select the classic block. After that, by clicking “Convert to block” displayed at the top of the block, it will be automatically converted to a block (lump).

It’s not a happy ending. As I mentioned earlier, I had some problems with the conversion (well, maybe 2000).

Although the introduction has become long, I will introduce some inconveniences (wrong conversion?) That occurred when I blocked old posts, so when converting on your site, the text content will not be strange. I hope you can use it as a checkpoint to do so.

Case where a block is erroneously converted with the “Convert to block” button

Is the part where the font size specified inline wrongly converted? Be done

If you specify the size and color of characters using span tags and inline CSS elements on a text editor, the character size may not be judged well and may be changed to relative sizes such as “xs” and “xxs”. was.

Perhaps the block editor’s judgment is that “it will be displayed but I do not know if it is okay to convert”, so it seems that it will be converted to extremely small size or extremely small size characters for the time being.

Of course, if this happens, the characters that you originally wanted to emphasize may be reversed, and the search engine may judge that the character size is unreadable and the quality is low, so be sure to preview it. Let’s check and fix it.

The position of the upper and lower paragraphs is out of alignment with the image

Probably because only the conversion from the text editor does not properly enclose the character string with the p tag on the text editor (I think that there are few people who put the tag because it is complemented in WordPress), but the image And the paragraphs below (or above) may be swapped.

This is hard to find on the edit screen, so be sure to read the full text in the preview and fix it.

The shortcode remains in the paragraph (no problem with operation)

The following conversion cases occur in posts with shortcodes inserted.

  • Converted to shortcode block (converted correctly)
  • Shortcodes are mixed in paragraph blocks

In either case, a valid shortcode will not stop working, but it’s a good idea to fix it to the correct form if possible.

Lists that are nested in a list are not represented well

It is a difficult matter to explain, but in short, if a list consisting of another list (child list) is converted in the li element of one list tag (parent list), erroneous conversion will occur. Occurs.

It seems that you can’t create a “list in a list” in the block editor, so you probably can’t convert it! Will judge.

In this case, it seems that somehow it is converted as follows.

  • The parent list is converted as it is with “・” as a list tag.
  • Child lists can be list tags, but all prefixes have a “1”

It seems that it varies depending on the list structure, so it is recommended to check it properly.

How was it? Did you think of any erroneous conversions?

There may be some erroneous conversions that you didn’t notice when you started converting on this site (some were discovered and corrected during the re-update), but let’s convert them steadily for the future.

Post Author: