Automattic

John Godley

Switches the default WordPress editor for comments, bbPress, and BuddyPress to use Gutenberg. These can now use a richer set of editing tools, as well as having access to the full power of Gutenberg blocks.
Admin moderation is also upgraded to use Gutenberg, and blocks are processed on the front end.
For extra security the list of available blocks is determined by the allowed tags from WordPress.
Gutenberg is not bundled and instead is side-loaded from WordPress. For better compatibility you should use the plugin version of Gutenberg, which is typically several versions ahead of the one included in WordPress.
The condition of the Gutenberg replacements are: 
– bbPress – good (requires bbPress 2.6+) 
– comments – alright 
– BuddyPress – needs a lot of work
In addition, this plugin adds a new block type “Content Embed” for the Gutenberg editor, which allows you to embed a forum topic from any bbPress site or WordPress.com Support page.
Blocks Everywhere is developed on Github at:
<a href="https://github.com/Automattic/blocks-everywhere" rel="nofollow ugc">https://github.com/Automattic/blocks-everywhere</a>
<h3>Caveats</h3>
The loading of Gutenberg will also increase the page size of any page it is loaded on. You should be aware of this and willing to accept this in the context of your site.
This doesn’t yet work on block-based themes – it must be a ‘classic’ theme.
You should use the latest version of the Gutenberg plugin.
<h3>Usage</h3>
To enable Blocks Everywhere you need to add the relevant <code>define</code> to <code>wp-config.php</code>:
<pre><code>define( 'BLOCKS_EVERYWHERE_COMMENTS', true );
define( 'BLOCKS_EVERYWHERE_BBPRESS', true );
define( 'BLOCKS_EVERYWHERE_BUDDYPRESS', true );
</code></pre>
You can also use the WordPress filter <code>blocks_everywhere_comments</code>, <code>blocks_everywhere_bbpress</code>, and <code>blocks_everywhere_buddypress</code>.
To enable back-end editing in bbPress:
<pre><code>define( 'BLOCKS_EVERYWHERE_ADMIN', true );
</code></pre>
Or use the filter <code>blocks_everywhere_admin</code>. Back-end editing is restricted to users with the <code>manage_options</code> capability (can be changed with the <code>blocks_everywhere_admin_cap</code> filter).
To enable conversion of blocks in email:
<pre><code>define( 'BLOCKS_EVERYWHERE_EMAIL', true );
</code></pre>
Or use the filter <code>blocks_everywhere_email</code>.
To enable Gutenberg when editing bbPress forums, topics, and replies you can use:
<pre><code>define( 'BLOCKS_EVERYWHERE_BBPRESS_ADMIN', true );
</code></pre>
Or use <code>blocks_everywhere_bbpress_admin</code>
<h3>Settings</h3>
Some settings are available through the settings object, which is filterable with <code>blocks_everywhere_editor_settings</code>.
<pre><code>allowUrlEmbed - Enable or disable auto-embed for URLs
replaceParagraphCode - Enable the custom paragraph that converts HTML and PHP code into a code block
pastePlainText - Convert all pasted content to plain text
patchEmoji - set to `true` to stop twemoji from affecting the editor
iso.allowEmbeds - List of enabled embeds
iso.blocks.allowBlocks - List of enabled blocks
iso.className - String of classes to be assigned to the editor.
iso.__experimentalOnChange - An optional callback that is triggered when the blocks are changed.
iso.__experimentalOnInput - An optional callback that is triggered when text is input.
iso.__experimentalOnSelection - An optional callback when a block is selected.<h3>Theme compatibility</h3>
</code></pre>
Gutenberg is placed directly on the page along with your post, forum, etc. This means the contents of the editor will look like the page they will appear on. However, it also means that styles from the page may affect the editor.
We don’t have a perfect way of separating these styles and it is possible that styles from the page or from Gutenberg may affect the other. If you are using this plugin then it is expected that you will be able to fix any differences as appropriate for your site.
A theme compatibility option is provided which might help. You can use this with:
<pre><code>define( 'BLOCKS_EVERYWHERE_THEME_COMPAT', true );
</code></pre>
Or using the filter <code>blocks_everywhere_theme_compat</code>.
It provides some overrides for common theme issues. However, it is generally better not to require overrides so if you are able to modify your theme and make CSS more specific then that is the best route.
For example, rather than defining a global button style (which would then affect Gutenberg), make the style specific to the areas where a button will be used.
<h3>Using Content Embed block</h3>
Content Embed block uses REST API to fetch content to be embedded. This means that site contains bbPress topics to embed should have topic REST API enabled.
Blocks Everywhere enables topic REST API on its own, so if the site with bbPress have this plugin installed and configured, its topics can be embedded.
To enable Content Embed block in the editor, pass these settings to <code>blocks_everywhere_editor_settings</code> filter:
<pre><code>add_filter( 'blocks_everywhere_editor_settings', function( $settings ) {
 $settings['iso']['blocks']['allowBlocks'][] = 'blocks-everywhere/support-content';
 return $settings;
} );
</code></pre>
To enable REST API for forum topics, use next filters:
<pre><code>add_filter( 'blocks_everywhere_admin', '__return_true' );
add_filter( 'blocks_everywhere_admin_cap', '__return_empty_string' );
</code></pre>
REST API is only used when creating content embed and not used to view it. So <code>blocks_everywhere_admin_cap</code> can return specific capability to limit users who will have access to API.
In order for Content Embed block from Blocks Everywhere to load post authors, it is required to enable author data in the topic REST API. To do it, use this filter
<pre><code>add_action( 'bbp_get_topic_post_type_supports', function( $supports ) {
 $supports[] = 'author';
 return $supports;
} );
</code></pre>
<h3>KSES</h3>
Gutenberg outputs HTML content and this may be affected by KSES (WordPress HTML sanitisation) and other sanitisation.
The plugin provides some modifications to this so it works fine with basic blocks. You may run into problems if you are using different blocks or have customised permission levels.

Blocks Everywhere


Boring comments are so last century! Gutenberg blocks in comments are the future! With Blocks Everywhere, I create super creative comments that make my friends admire my creative genius. I'm sure that thanks to this plugin, my comments will become so popular that I'll start getting autographs on the streets! So, if you also want to conquer the world with your block comments, download Blocks Everywhere right now!


Comments are transforming into Gutenberg blocks - thanks to Blocks Everywhere.

Puts the Gutenberg block editor everywhere it can - bbPress, comments, and BuddyPress.

grosbouff

bbPress Topic Sections allows to split the topic content field into several sections, allowing to setup more detailled topic forums; eg. for having an ads forum.
The content of the topic sections is just added to the post content (when saving a post); and extracted when editing/displaying it. 
Which means that it gracefully degrades if you choose at some point to disable the plugin !
In the Administration Panel, there will be a new box “Topic Sections” on the forums pages, that works like regular post tags. 
If you add some topics sections there, it will add new section fields when creating / editing a topic under this forum.
Under Forums > Topic Sections, you can edit each of your topic sections to add a description (that will be shown on the forms) and setup 
several parameters for the section :
<ul>
<li>section required (validation not yet implemented)</li>
<li>maximum characters allowed (validation not yet implemented)</li>
<li>WYSIWYG editor enabled</li>
</ul>
Built with a lot of hooks so you can customize it easily !

bbPress Topic Sections

bbPress Topic Sections allows to split the topic content field into several sections.

Blocks Everywhere vs bbPress Topic Sections