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 …
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:
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 development code and issue tracking.
It’s easiest to use the built-in plugin installer inside WordPress. Go to Plugins > Add New, and search for “lock pages”.
To install manually:
lock-pages
folder into your site’s /wp-content/plugins/
folder.That’s it!
The definition of who is able to move or delete locked pages is made via a plugin setting that specifies a capability. This also defines who can edit the plugin’s settings, and who can lock individual pages. Be careful not to bar yourself!
It defaults to manage_options
, which by default is only granted to the Administrator role, but it can be changed. You will get a warning if you enter a capability that doesn’t exist in your system.
Lock Pages will work with Justin Tadlock’s Members plugin, if it’s installed, to respect any custom capabilities you may have entered.
No. I’m having problems getting this working properly. Until then, sadly, I’ve had to remove the Quick Edit link from locked pages for users who are barred from changing locked page attributes. Sorry! They can still edit other things with the normal edit screen.
I feel I gain more than enough already from the WordPress community in monetary terms, through the work it lets me do and the services it lets me offer. For me, part of writing a plugin is precisely to give back to the community – so it seems odd to ask for money for a small plugin (even if it’s not obligatory).
Still, I know that sometimes a plugin really makes your day and you want to give back in turn. If this plugin tickles you and you feel like giving, I’ve given the link to donate to Corporate Watch, who perform what I think is a hugely important role in holding large corporations to account.
Of course, contributing back to the WordPress community is also a great way to express gratitude for a plugin!
user_has_caps
filter, and issue with arrays passed for $args[0]
wp_dropdown_pages
$thispluginurl
and $thispluginpath
, introduced use of plugins_url
$args
in lock_deletion
to account for different user_has_caps
contextsadd_options_page()
to match the capability setting in the plugin, i.e. only users with the capability to edit “locked” pages can change the plugin settings.