Ryan Street

Show or hide content with a simple to use shortcode system. You can access or restrict content for:
<ul>
<li>Logged in/out users</li>
<li>different user types, (author, administrator, etc.)</li>
<li>different user roles and capabilities</li>
<li>URL Keys</li>
<li>password entry (good to show teasers, etc)</li>
<li>show/hide clickable links</li>
</ul>

Content Lock

Show or hide some or all of your content by wrapping it in convenient shortcodes!

Marie Comet

Lock Reusable Blocks in the editor to avoid unintentional global changes. 
Editing reusable blocks in posts is locked, and you have access to two actions when you select a reusable block in the editor: 
– Edit the reusable block (opens the block editing page in a new tab) 
– Convert to regular blocks (native action)
Options are availables in Settings > Writing screen to hide Edit and Convert reusable blocks buttons in block overlay.

Lock Reusable Blocks

All plugins should be like this. Simple one job plugins that do one thing well. I follow this philosophy in my own plugins and it is good to see others doing the same.

Good plugin


This should be a feature of WP and not a plugin. It's really useful for building large sites and not having clients mess them up afterward due to the ability to edit useable blocks.


Should be a feature of WP and not a plugin


This plugin doesn't get enough attention. THIS is the way reusable blocks are supposed to work. Letting the user know what they are doing: editing the reusable block side wide, or just editing a single instance. Clean, simple, obvious. Couldn't be better!



I have been following the problems with reusable blocks for years now. On Github there seems to be a consensus that this issue is somehow resolved since block locking became a feature. But still, it is way too easy to accidentally edit reusable blocks in an unintended way, even with WP 6.2. Actually it used to be good when Gutenberg just released. Back then, reusable blocks where one of the few features that they completely nailed from the start. Why this was changed in such a bad way, is a complete mystery to me.



Thanks for writing this essential plugin. Hope it makes it into core!


Content Lock vs Lock Reusable Blocks