Steve Taylor

<p>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.</p>
<p>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”.</p>
<p>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.</p>
<p>This plugin lets administrators “lock” any or all pages, and any post of any post type. “Locking” here basically means preventing non-admins from:</p>
<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>
<p>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.</p>
<p>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.</p>
<p>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>.</p>
<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 …

webdevstudios

Michael Beckwith

pluginize

modemlooper

Brad Williams

John Hawkins

<p>Custom Post Type UI provides an easy-to-use interface for registering and managing custom post types and taxonomies for your website.</p>
<h4>Custom Post Type UI Extended</h4>
<p>CPTUI helps create custom content types, but displaying that content can be a whole new challenge. <a href="https://pluginize.com/plugins/custom-post-type-ui-extended/?utm_source=cptui-desription&utm_medium=text&utm_campaign=wporg" rel="nofollow ugc">Custom Post Type UI Extended</a> was created to help with displaying your crafted content. <a href="https://pluginize.com/cpt-ui-extended-features/?utm_source=cptui-description-examples&utm_medium=text&utm_campaign=wporg" rel="nofollow ugc">View our Layouts page</a> to see available layout examples with Custom Post Type UI Extended.</p>
<h4>Plugin development</h4>
<p>Custom Post Type UI development is managed on GitHub, with official releases published on WordPress.org. The GitHub repo can be found at <a href="https://github.com/WebDevStudios/custom-post-type-ui" rel="nofollow ugc">https://github.com/WebDevStudios/custom-post-type-ui</a>. Please use the WordPress.org support tab for potential bugs, issues, or enhancement ideas.</p>


Custom Post Type UI

Works well, but it's missing a number of CPT options: rest_namespace, capabilities, map_meta_cap, register_meta_box_cb, rewrite[feeds, pages, ep_mask], template, and template_lock. I realize these are not common, but it's a drag when you go to create your third CPT and realize you need to find a different solution that will accommodate one of the missing options. It's no good to have a few registered in CPTUI and a few by hand.

Good, but missing a bunch of options.


There is no documentation. In plugin description there is just a link to so called documentation that is just bunch of tutorial of doing specific stuff that are very scarce and targeted to people who already know how to use it. Nothing for first time users, to learn how to actually begin with plugin, or at least nothing that can be easily found.


One of the worst documented plugins I saw


Thank you very much for this amazing Plugin that serves us since years!


Amazing Plugin


speeds up development and has nice user-friendly UI. It was a nice experience working with this plugin.


really useful


Plugins like these make wordpress worthwile


Great piece of software

Admin UI for creating custom content types like post types and taxonomies

Lock Pages vs Custom Post Type UI