Seeing the same problem on a client site, where they’ve been reluctant to fully move to the block editor — but I’m telling them the time has come. Content created with Advanced Editor Tools isn’t displayed at all in the editor under WP 7.1 unless you switch from visual to code view.
I created a quick and dirty plugin that strips out all of the block comment tags for the “advanced” editor, which is how I would recommend solving the problem. Code here
https://gist.github.com/davidfcarr/c6b174da4cf395fe2492c4516f390bec
Demo of using this on a client site
https://www.youtube.com/watch?v=hnlSZ7R9BeU
Hi @davidfcarr, thanks for your plugin. In any case, I also think it’s time to use WordPress’s native “Paragraph” plugin.
In my case, given my many posts, I’ll convert them from time to time if necessary to avoid problems with images, etc., as I saw in your video. Now I’ll start writing new posts with “Paragraph.”
I use this plugin too and have a fix in my git repo that seems to get it going again, if anyone is interested – it works for me, at least (and also should on older WP 5.9+). Hopefully an official fix will be out soon!
Quick note on what it does: WordPress 7.1 always puts the editor canvas in an iframe, which the Classic Paragraph block’s TinyMCE can’t attach to – that’s why the blocks look empty. With the fix, the block shows its content as a preview in the canvas and opens TinyMCE in a modal when you hit Edit – the same approach core’s Classic block uses. Existing content is untouched.
The git repo is created from subversion but only from 5.9.2 because svn is sooo slow.. I really wish there was an up-to-date git mirror (I forked from the old mirror to at least keep a link somewhere). I may update the branch if I manage to mirror the full trunk history.
Feel free to take the patch and apply it to your own version of the code, svn checkout of 5.9.2 or whatever you want to do. It’s GPLv2.
Here is the fork and branch:
https://github.com/csmart/tinymce-advanced/tree/fix/classic-paragraph-iframed-editor
If you want to use my branch directly from git, then something like this should work – clone the branch, create a zip and then upload it, replacing the installed version:
$ git clone \
-b fix/classic-paragraph-iframed-editor \
https://github.com/csmart/tinymce-advanced.git
$ cd tinymce-advanced
$ git archive \
--format=zip \
--prefix=tinymce-advanced/ \
-o ~/tinymce-advanced-wp71-test.zip \
HEAD
Then upload the zip file through Plugins -> Add Plugin -> Upload Plugin -> Choose file -> Select the zip from file picker -> Install Now -> Replace current with uploaded. If it worked, the Plugins screen will show version 5.9.3-wp71-test.
Update: the git-svn clone of the full trunk history finally finished, so the fix branch now sits on top of a proper clone of current trunk instead of a flat 5.9.2 snapshot (trunk only differs from the 5.9.2 release by readme “tested up to” updates and a typo fix, so it’s the same plugin code). Same branch and instructions as above, but it was a force-push, so if you already cloned, do a fresh clone rather than a pull (or fetch and reset).
I’m not dismissing anyone’s concerns, only offering a solution I used to resolve this on a small business client site. For some of you, the scale of the issue is much different. I agree the plugin developer should be providing its own solution, particularly since this is an Automattic plugin that you would think should have been tested with 7.1.
I’ve archived many of the replies because they were not helping as much as they were venting. And randomly @’ing people is really not cool at all. Those replies have been removed.
If you mean to help via a patch, a work around, or a fix, that’s amazing and welcomed.
If you are using this and other topics to vent, to call out people and complain, please do not repeat that again. That will lead to this topic being closed. If you need support for your problem then consider posting your own topic and not take over someone else’s.
I created a new release. The classic paragraph block now works just like the classic/freeform block and should no longer disappear.
