Steve Taylor

NOTE: This plugin is not tested with Gutenberg, and we have no near-term plans to do so. If using WP > 5.0, use the Classic Editor if there are problems.
NOTE: This plugin was originally designed to only lock pages, and only later added custom post type functionality. Hence the name, and sometimes the terminology will say “pages” when it means “any post type”.
Sometimes some pages or other posts are too important to allow them to be casually moved about or deleted by site editors. An editor may think nothing of renaming a page’s slug, or deleting a page to replace it with something similar, perhaps unaware of effects on SEO. Also, certain pages might be essential to keep in place because of a site’s structure, or because of aspects of a custom theme.
This plugin lets administrators “lock” any or all pages, and any post of any post type. “Locking” here basically means preventing non-admins from:
<ul>
<li>Editing the item’s slug</li>
<li>Changing the item’s parent</li>
<li>Changing the item’s template</li>
<li>Deleting the item</li>
<li>Changing the item’s status</li>
<li>Changing the item’s password protection</li>
</ul>
Locking is implemented by preventing the actual database update being performed as well as, where possible, having the interface element for that field removed. Where possible interface elements are removed via WP filters on the server; otherwise, jQuery is used on the client.
NOTE: Currently, I’ve been unable to get this working with the Quick Edit functionality. As a stop-gap measure, which is only in place because it seems to be better than nothing, the Quick Edit link is removed for users who can’t edit locked pages. I know, it’s not great. But until I work out how to selectively block Quick Editing, I’m assuming a locked page should be locked. Users can always edit the other fields via the normal edit page.
Go to GitHub for <a href="https://github.com/gyrus/Lock-Pages" rel="nofollow ugc">development code</a> and <a href="https://github.com/gyrus/Lock-Pages/issues" rel="nofollow ugc">issue tracking</a>.
<h3>Known issues</h3>
<ul>
<li>Quick Edit presents problems. I’ve worked out how to create hidden fields in the Quick Edit box, and to put the values in the hidden div, but I can’t work out how to dynamically populate the fields with the values, so the old values can be used if necessary on saving. For now Quick Edit is blocked for users who can’t edit locked pages.</li>
<li>Although I’ve fixed the lock_parent function so it allows uploaded files to be attached to a locked page, it still prevents media already in the library from being attached when inserted.</li>
</ul>
<h3>Ideas</h3>
<ul>
<li>Include the locking checkbox for admins in the Quick Edit form.</li>
<li>On the settings screen, use a drop-down for selecting which capability is needed for editing locked page elements.</li>
<li>Implement a system to deal with descendants, e.g. an option to lock all descendants of a locked page or not.</li>
</ul>

Lock Pages

Lock Pages prevents specified pages (or all pages), posts, or custom post types from having their slug, parent, status or password edited, or from bei …

mobde3net

ePermissions plugin allows you to manage your members (who have Editor role) and you can make for them capabilities that you choose only for them.
Also, you can use ePermissions plugin to choose any permission added by this plugin to select some roles or options for editors on your blog. Permissions
have 6 options about editors such as, controlling in links, comments, posts, pages and files uploaded. Motioned options are currently available as
ePermissions, these options are giving you the ability to show/hide some available capabilities for Editor role in WordPress platform.
In this version, Arabic and English are the available languages . If your WordPress version is English then ePermission language will be English
automatically. The same goes for the Arabic.
<h4>Features</h4>
<ul>
<li>
Hide and show capabilities in sidebar.
</li>
<li>
Disallow access to capabilities pages. (if the permission has capabilities that considered as unchecked where is not allowed)
</li>
<li>
You can write a permission message for a member who has permission, and the message will be on the top of admin pages. (this is optional field, I will try to improve current message shape)
</li>
<li>
You can open and close the permission, and the member who has closed permission can get all capabilities. (For Editor role)
</li>
</ul>
You can send me an email for any suggestions about ePermissions plugin at: mobde3net[at]gmail.com.

ePermissions

ePermissions plugin allows you to manage your members (who have Editor role) and you can make for them capabilities that you choose only for them.

Lock Pages vs ePermissions