Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records Private Page Forbidden version 0.2 as active, updated 17y ago and tested up to WordPress 2.8.
Overview
About this plugin
This plugin is developed at Shepherd Interactive
for the benefit of the community. No support is available. Please post any questions to the support forum.
php if it exists.
Provides a filter forbidden_redirect which if results in a non-empty filtered value will result in the user being redirected if attempting to visit a forbidden page; the default value is "" (no redirect).
Useful with a filter which selectively prevents a private post from being forbidden, so that the page will not show up in the navigation and won’t be included in XML Sitemaps, for example.
function my_filter_private_posts($posts){ if(is_singular() && $posts[0]->post_status == 'private' && #Now optionally allow/disallow based on user session: in_array($_SERVER['REQUEST_URI'], (array)@$_SESSION['allowed_private_uris'])) ){ header('Cache-Control: private'); #Prevent proxies from caching this private page $posts[0]->post_status = 'publish'; } return $posts; } add_filter('posts_results', 'my_filter_private_posts');
WordPress.org metadata
Plugin tags
Topics listed for this plugin in the WordPress.org directory.
access control
403
Compatibility & maintenance
Compatibility & maintenance
Tested up to WordPress 2.8
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 2.8.
Current WordPress releaseWordPress 7.1
WordPress.org Tested up to2.8
Minimum requirementsWordPress 2.7 · PHP not listed
Update activity28 Sept 200917y ago
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
Changes recorded by WP PlugIndex
Recent tracked changes
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
Tracking & source
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.