We’ll be handing a site over to clients soon (eek) and there are bits of content on pages we DONT want them to change (accidently or otherwise).
Without getting all fancy and building every page from a million custom fields, is there a way to tag/flag page elements as locked like the class library can?
I’ve tried using components, but that doesn’t cover every possibility and removes a bunch of flexibility - need to set up so many versions and field groups. Some pages have custom built stuff (due to my time, and designer wanting some flair!), which ideally we could lock for non admins?
I think you can not do it like that.
Or he has builder access, or he does not.
Give everything a proper identifying name and make sure to have backups.
Maybe put the complex stuff inside a template and tell him not to touch them, while the stuff he is allowed to touch is on the normal page.
Yep, I’m aware they shouldn’t touch things, but some designers/clients will still quite happily mess up a site if left to roam free!
The class locking (and permissions to stop them unlocking a class) has helped in that classes arent being changed while the site is still in development mode and leading to a lot of confusion, unless I change them. Components dont work for super complex setups and queries. A lot of the site is templated out using ACF Pro fields, but its’ not realistic to do everything there (and it would take forever).
The ability to set a permission level to not touch certain things would be great (right click and ‘lock’ a section/block, and unlock elements in it? Not too sure how the flow would/should work for this user case.).
So clients can still update text, drop in new templates, build new pages using templates (not that they really should be adding new pages after the weeks of discovery and IA and UX and design, but reality is they will over time)… and not break/change critical parts that are there for a reason.
Would be a nice feature to add, but yes could be a tricky one to get right.