One of my favourite things about building for WordPress is how quickly a bit of feedback can turn into a real feature. This week it happened again.
A few days ago, Alessio left a lovely review of Jamie’s Front-End Editor for Content Teams:
“Very promising plugin, exactly the kind of thing I am looking for for my next client. So far the only issue I have is that you can’t lock / prohibit editing of an entire page or the content inside a specific container of a page. More finesse in the editing scope would be awesome.”
Alessio
That’s a great point, and honestly the missing piece for real client work. Letting a content team fix the copy is wonderful, right up until someone accidentally rewrites the call to action or the legal footer. You want them editing the bits that should change, and nothing else.
So that’s exactly what version 0.3 adds: editing locks.
There are three ways to lock things down, and you can mix and match them:
Lock a whole page. Open any page and tick “Lock this page” in the new Front-End Editing box. The front-end editor simply won’t appear there.
Lock a single block. Use the block’s own Lock option, the little padlock in its Options menu. That block becomes read-only on the front end.
Lock a whole section. Lock a Group (or add the CSS class fie-no-edit to it) and everything nested inside it is protected in one go. Perfect for fencing off a hero, a pricing table, or a footer.
The important part: these aren’t just hidden in the interface. Every lock is enforced when content is saved, so a locked block or page can’t be edited even by poking at the API directly. Locked means locked.
Thank you Alessio, this one’s for you. If you’re using the plugin and there’s a rough edge or a missing piece, leave a review or a support note. That’s genuinely how this thing gets better.
Version 0.3 is live on WordPress.org now.
Leave a Reply