Jan Štětina

Warning: This plugin is currently broken (at least for some sites) and I have no time to maintain it. I plan to solve all the issues from the support forum but I have no idea when that might happen (perhaps summer 2014). I am sorry and thank you for the understanding.
Provides a system for registration requests and their processing in multisite.
Blog administrator can place a shortcode <code>[murm-form]</code> on their blog, which will display a registration form. Visitors can then use this form to request registration. Such a request must be first moderated by the blog admin. If it is accepted, it’s passed on to the blog superadmin, who also has to approve it in order to pass. After approval the plugin creates given user accounts with subscriber rigths on the blog from which it was requested and sends login information to the user.
Per-blog settings
<ul>
<li>can be deactivated</li>
<li>notification via nag or e-mail on new requests</li>
<li>antispam (needs Akismet API key)</li>
<li>requests on the blog admin level can be automatically approved</li>
</ul>
Per-site settings
<ul>
<li>optional e-mail notifications</li>
<li>custom e-mail templates</li>
<li>blog administrators can be allowed to delete a request without notifying it’s author</li>
<li>requests on the network admin level can be automatically approved (this means that only blog administrators decide about their requests, if no error occures)</li>
</ul>
This plugin was developed for a small blog server (cca 30 blogs), so that superadmin would have control of newly created accounts (because some people were confused and got themselves unneccessary multiple user accounts).
Makes use of the <a href="https://wordpress.org/extend/plugins/wordpress-logging-service/" rel="ugc">WordPress Logging Service</a>.
In future there will be more options to modify default plugin behaviour.
<h3>Wishlist</h3>
Below are listed requests I know about and I’m going to process… eventually. Please be VERY patient.
<ul>
<li>“I have a request of asking for password on registration form. That way the user can pick out a password and have it automatically populated in the site user data.”</li>
<li>sidebar registration widget</li>
<li>attach custom admin message to user on request approval/denial</li>
<li>correct i18n, custom blog admin messages</li>
<li>custom shortcode css (error/ok) + information</li>
<li>save all settings as a single wp option</li>
<li>combine with pure-murm?</li>
<li>“I would like to add more fields like “country” in the Registration Page.”</li>
<li>custom new user default role</li>
<li>recaptcha on registration</li>
</ul>

Multisite User Registration Manager

Worked for me

Provides a system for registration requests and their processing in multisite. Two-level moderation.

unCommons

Gutenberg is a great editor but sometime you could want to disable it for Pages, Posts or other post types. Gutenberg Manager allow you to enable/disable the editor where you want. Why would you want to disable the editor on pages? Maybe you would like to use a page builder like Visual Composer or Elementor instead!
Gutenberg Editor will be probably included in the next great release of WordPress (5.0) so Gutenberg Manager will be really useful. With the Manager you can also decide to disable specific blocks in the editor if you don’t need them.
If you are developing or editing a theme/plugin all features are also available via Hooks so you can include Gutenberg Manager plugin inside your theme and use it without the Option Panel.
If you like this plugin, please give us 5 star to encourage for future improvement.
<h3>How to use</h3>
Under “Gutenberg” menu in your dashboard you’ll find a new button “Gutenberg Manager”. This is the Option Panel of our plugin. For now it includes 4 options areas:
<ol>
<li>Settings</li>
<li>Default Blocks</li>
<li>Additional Blocks</li>
<li>API/Hooks</li>
</ol>
SETTINGS 
Here you can globally disable Gutenberg Editor or manage the visibility of editor in the different post types.
DEFAULT BLOCKS 
Here you can disable the default blocks in the Editor.
ADDITIONAL BLOCKS 
Here you can enable our additional blocks in the Editor. 
This section is under construction
API/HOOKS 
Here you find a list of Hooks to use in your custom Theme/Plugin! 
Note: there is an action to disable the Option Panel of Gutenberg Manager so our plugin will be hidden for the final user but the theme/plugin developer can use all the plugin’s features.

Gutenberg Manager

Gutenberg comnpletely mangles custom handmade HTML, which depends on being treated as raw HTML. If hand-coding or the classic TinyMCE editor is not enough or not right for a client, then I pep things up with a shortcodes plugin like shortcodes ultimate or even WP Bakery Pagebuilder. Gutenberg will basically trash all my strategies and I can't rewrite all my client websites when 5.0 comes out. There is another plugin "Disable Gutenberg" but this one offers many more options. Sadly, neither of them offers to turn off Gutenberg on a per-page basis, which would be really nifty.

Great job, I'll really need this for WP 5.0

A simple and easy way to manage Gutenberg editor. You can disable/enable it for every post types and restore the Classic Editor.

Multisite User Registration Manager vs Gutenberg Manager