Skip to content

Category Archives: Development News

Yoast SEO Sitemap Integration

Press Permit Pro has been updated for Yoast SEO Sitemap integration. Posts which are not universally visible due to restrictive Press Permit exceptions are now excluded from the Yoast sitemap. Both post-specific and category or term-based exceptions are considered. Media attachment restrictions imposed by the PP File URL Filter extension are also applied to the sitemap. To enable this functionality, install or update the PP Compatibility Pack extension plugin.

WP 5.0

Today’s Press Permit Core update marks official compatibility with WordPress 5.0.

See details about Gutenberg compatibility in this FAQ. For further details, see the change log on

Gutenberg Update

PP Collaborative Editing Pack 2.5.1 fixes an issue with Gutenberg editing by non-Administrators. Save / publish operations required an additional click after failing on the first attempt.

PHP 7.2

Press Permit Core and all the Pro extension plugins have been updated for PHP 7.2 compatibility.

For further details, see the change log on

WP 4.9

Press Permit Core 2.4 is released. It includes WordPress 4.9 compatibility, improvements to the page / term selection UI for editing group permissions, and a number of significant performance improvements. Bug fixes include corrections to REST handling. For details, see the change log on

WP 4.8

Press Permit Core 2.3.19 includes some minor changes for WordPress 4.8 compatibility.

WP 4.7

Press Permit Core and the Pro extensions have been updated for compatibility with WordPress 4.7.x and PHP 7.1

New: bbPress Teaser

Does your membership site feature private bbPress forums?  Would you like an easy way to let visitors see a list of those private forums and click in for a preview?  How about displaying the forum statistics and topics, but masking the replies?  It would help people recognize how much useful feedback you’ve been providing. Press Permit Pro is now ready to help.  Introducing bbPress Teaser!

Settings are located alongside the teaser controls for other post types after enabling the PP Content Teaser and PP Compatibility extensions.  You can configure it to tease replies only, or both topics and replies. If you prefer to hide both topics and replies completely, a dedicated teaser-content-forum template may be added to your theme folder.

Here’s how the new switches look in the Press Permit Pro settings panel:
Settings: bbPress Teaser

You can specify your desired teaser text for replies and (if enabled) topics within the plugin settings UI:
Teaser Text: bbPress Teaser

Press Permit does not handle member registration and billing, but this bbPress content teaser could be a key element in your membership solution.  See it in action on the Press Permit Pro member support forums:
Example Forum: bbPress Teaser

WP 4.5, PHP 7

Press Permit Core 2.3.9 resolves a few issues with WordPress 4.5 and PHP 7 compatibility. New features include a sortable Groups column on the Users screen, updated WP-REST v2 compatibility (Pro w/ PP Collaborative Editing extension) and support for some new Hidden Content Teaser options (Pro extension). Pro users have several extension updates available.

WP 4.4, REST API support

Press Permit Pro now includes preliminary support for the new WordPress REST API. This provides a direct http interface to WordPress data, allowing for a decoupled architecture which appears to be the future of WordPress and much of the web. Although the current WordPress release (4.4) does not actually implement this API, you can activate the REST API (version 2) plugin to activate the endpoints to make it work. These are presumably similar to the default endpoints which will be included in WordPress 4.5.

Press Permit Pro development and testing to date has been against the REST API 2.0-beta9 plugin. Filtered data includes Posts, Terms and Post / Term relationships accessed through the standard WP_REST_Posts_Controller, WP_REST_Terms_Controller and WP_REST_Posts_Terms_Controller endpoints. Retrieval, creation, editing and deletion of this content is filtered and regulated to match your site’s normal front end and wp-admin access. For testing, I used the Postman extension for Chrome. I couldn’t get the user authentication working in a reasonable time, so I just implemented my own temporary authentication based on an http argument.

Here are a few notes on implementation:

In the current beta version of REST API, to remove post terms you must pass the force argument:
DEL /wp-json/wp/v2/posts/1/categories/?force=1

When using the REST API to retrieve posts or terms, the default behavior is to treat it as a “front end” result set. All readable items are returned. To allow for voluntary “What you see is what you can edit” filtering, I have implemented the following nonstandard http argument: operation.

To return editable pages:
GET /wp-json/wp/v2/pages/?operation=edit

To return assignable categories:
GET /wp-json/wp/v2/categories/?operation=assign&post_type=post

To return manageable categories:
GET /wp-json/wp/v2/categories/?operation=edit