Skip to content

Frequently Asked Questions

Is Press Permit licensed as GPL?

Yes, Press Permit is released under the GPL version 3 license (the same as WordPress).

Purchasing a support key entitles you to receive your initial download from a trusted source (the author), one-click updates and extension installations within your WordPress site admin, plus 12 months of expert support through our convenient ticket system.

A developer support key provides a year of updates to up to 25 installations (no limit to number of networked sites), plus our fond regards.

Is the Gutenberg editor supported?

Press Permit Pro supports the new WordPress editor, Gutenberg – with one caveat. Reading Exceptions, Editing Exceptions and other Press Permit metaboxes are fully operational on a Gutenberg edit screen.

Note, however, that Gutenberg does not currently support custom post statuses. If the PP Custom Post Statuses extension plugin is activated, the classic editor will be used. To re-enable Gutenberg for a specific post type, you can disable custom statuses for that type.

What WP versions are supported?

We are committed to providing compatibility with upcoming WordPress releases. As of the last update to this page, Press Permit has been tested up to WordPress 5.1.

See details about Gutenberg compatibility here.

PHP versions 5.2.4 to 7.2.x are supported.

bbPress version 2.0 to 2.5.x is required to grant forum-specific permissions to specific users or groups.


How does Press Permit compare to Capability Manager and other role editor plugins?

Press Permit’s functionality is different from and complementary to a basic role editor / user management plugin.  In terms of permissions, those plugins’ primary function is to alter WordPress’ definition of the capabilities included in each role.  In other words, they expose lots of knobs for the permissions control which WordPress innately supports. That’s a valuable task, and in many cases will be all the role customization you need.  Since WP role definitions are stored in the main WordPress database, they remain even said plugin is deactivated.

Press Permit can assist you in turning the site-wide capability knobs for desired post types. But it also supercharges your permissions engine. Press Permit it is particularly useful when you want to customize access to a specific post, category or term. Extension plugins add collaborative editing control, file filtering and other features which are not otherwise possible. The plugin will work with your WP roles as a starting point, whether customized by a role editor or not.  Users of the PP Collaborative Editing extension can (after activating advanced settings) navigate to Permissions > Settings > Role Usage to see (or modify) how Press Permit is using your WP role definitions. Press Permit’s modifications remain only while it stays active.

July 2012 update: see Capability Manager Enhanced.

Is Press Permit an out-of-the-box membership solution?

No, but it can potentially be used in conjunction with an e-commerce or membership plugin. If you have a way to sell users into a WordPress role or BuddyPress group, Press Permit can grant access based on that membership.

Where does Press Permit store its settings? How can I completely remove it from my database?

Press Permit creates and uses the following tables: pp_groups, pp_group_members,  pp_conditions, pp_roles.  Press Permit options stored to the WordPress options table have an option name prefixed with “pp_”. Due to the potential damage incurred by accidental deletion, no automatic removal is currently available.  You can use a SQL editing tool such as phpMyAdmin to drop the tables and delete the pp options.

If you set posts to a custom Visibility status, be sure to change them back to Private or Pending before permanently deactivating Role Scoper.

I have more questions!

Feel free to contact us with any questions about Press Permit or other PublishPress solutions.