Lock Reusable Blocks

Before this plugin, I'd spent hours redoing work on my Reusable Blocks I had accidentally overwritten or completely deleted. Wish I could go back in time and tell myself to install this plugin as soon as I started! Easy install, clear UI, is working perfectly with my other plugins and my theme & WordPress version (Twenty Twenty-Three; v6.1). As others have said, this plugin should be a feature by default. I'm not blogging without it ever again!

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!

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.

This is the design that should the reusable blocks have out of the box!

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.

Even people who understand the concept of reusable blocks tend to unintentionally edit such blocks from time to time (changing it for the whole website instead of a single instance). This plug-in protects reusable blocks in simple, elegant way – and you can still edit them if this is really your intension. Should be integrated into WP core.