Francesco Pesce

Nerds Farm

Rabbit Hole is a plugin that adds the ability to control what should happen when an entity is being viewed at its own page.
Perhaps you have a content type that never should be displayed on its own page, like an image content type that’s displayed in a carousel. 
Rabbit Hole can prevent this object from being accessible on its own page, through p=xxx (or permalink).
Options
This works by providing multiple options to control what should happen when the entity is being viewed at its own page. 
You have the ability to 
– Deliver an access denied page (401, 403). 
– Deliver a page not found page (404). 
– Issue a page redirect to any path or external url (301, 30x). 
– Or simply display the entity (regular behavior, 200).
This is configurable per: 
– post type and single post. 
– taxonomy and single term 
– roles and single user
It’s possible to generate dynamic values with Twig or Shortcode for the redirect path. 
This makes it possible to execute different redirects based on whatever logics you need. 
Perhaps you want a user to be able to view nodes that he has created, but no one else’s.
New options: 
– Archives 
Support for Terms and Authors archive pages 
– Conditions 
There will be the possibility to configure a User Role that override Rabbit Hole completely, useful for Memberships. 
– Display Message 
Show a custom Message for unauthorized page (401, 403)
Drupal porting 
This is porting from a beloved <a href="https://www.drupal.org/project/rabbit_hole" rel="nofollow ugc">Drupal module</a> which I used in all my projects. 
Thanks to the authors for the idea.

Rabbit Hole

Control what should happen when an entity is being viewed at its own page

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.

Rabbit Hole vs Gutenberg Manager