Hello @hebhansen,
the “Blocks Everywhere” plugin is no longer actively maintained. It is only infrequently updated for compatibility with Gutenberg, but as you probably saw, last time that happened was over 1.5 years ago.
For bbPress compatibility, there’s a long-standing Trac ticket and patch in bbPress’ Trac system. For frontend comments, the ideal scenario would probably be for Gutenberg to support blocks natively in the comment form, but I haven’t found any related GitHub issues or other plans. I’m not sure what’s the state of frontend block support in BuddyPress. (I realize that none of these are immediately helpful if you’d like to use the block editor on the frontend right away, but I wanted to give an overview of where things are at.)
Regards
Bernie
Hi @bernhard-reiter
Thx for elaborating. That’s exactly what I was looking for. Just an understanding of …. So I guess, there’s nothing to do than wait around. So this conclusion means that this site ww.wp.xz.cn uses an antiquated Gutenberg?
Dear Automatic – Please lift the editor I am currently editing in, into core bbpress/gutenberg thx
So this conclusion means that this site ww.wp.xz.cn uses an antiquated Gutenberg?
Unfortunately yes, the ww.wp.xz.cn Support Forums specifically use Gutenberg 17.9 at present due to this compatibility constraint. We’d like to replace the Blocks Everywhere integration on the forums with another solution, preferably natively supported by bbPress, but we don’t have a timeline on this at present.
We use the latest releases of Gutenberg everywhere else on ww.wp.xz.cn.
@dd32
ok, I see and now I’m puzzled… How are you running 2 different Gutens on the same ww.wp.xz.cn install?
that could sound like a solution. Is the antique Guten also used for frontend comments?
@hebhansen Apologies, I was on holidays.
ww.wp.xz.cn uses a Multisite architecture, as such, ww.wp.xz.cn vs ww.wp.xz.cn/support are two different “Sites” each with their own set of plugins.
It is possible to use a mu-plugin to load a different plugin based on the URL being viewed though, but I would suggest NOT doing this on different paths of a single site. See [1] [2]
