Plugin profile · observed daily since 02 Aug 2026
Restrict – membership, site, content and user access restrictions for WordPress
Active installs2,000+ rounded
Current authorTickera
Owner changesNone while we have been watching
Last release10 days ago 26 Aug 2026
Support— no recent threads
Releases on record11
Rating4.2 /5 · 25
Added to directory10 Oct 2016
Requires WP5.1
Requires PHPfalse
Version lag0 up to date
Tested up toWP 7.1 up to date
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Tickera throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| tickera | 10 | 16 Oct 2024 | 24 Jul 2026 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Moderately adopted: 2,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
49 downloads a day over the last 7 days, falling 64% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 700/day05 Sep 2026
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep | 05 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 11 | 46 | 22 | 72 | 700 | 74 | 34 | 47 | 70 | 50 | 59 | 45 | 35 |
| Version | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 |
Unchanged throughout: ratings total (25) · active installs (2,000+) · support threads (0) · threads resolved (0)
35 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory9.5 years ago 10 Oct 2016
Requires WP5.1
Requires PHPfalse
Version lagcurrent
Is anyone still maintaining this?
- Last released 26 Aug 2026, 11 days ago.
- Declares compatibility with WordPress 7.1, which is current.
- The same account maintains 1 other plugin, 1 of which was updated in the last 90 days. the account is active.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 26 Aug 202611 days agoVersion 2.4.1 released
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 24 Jul 20261 month agoVersion 2.4.0 released
- 25 Jun 20262 months agoVersion 2.3.5 releasedfrom the release logCommitted by tickera.
- 08 Jan 20268 months agoVersion 2.3.4 releasedfrom the release logCommitted by tickera.
- 19 Feb 202519 months agoVersion 2.3.3 releasedfrom the release logCommitted by tickera.
- 17 Feb 202519 months agoVersion 2.3.2 releasedfrom the release logCommitted by tickera.
- 27 Jan 202519 months agoVersion 2.3.1 releasedfrom the release logCommitted by tickera.
- 30 Dec 202420 months agoVersion 2.3.0 releasedfrom the release logCommitted by tickera.
- 03 Dec 202421 months agoVersion 2.2.9 releasedfrom the release logCommitted by tickera.
- 28 Oct 202422 months agoVersion 2.2.8 releasedfrom the release logCommitted by tickera.
- 16 Oct 202423 months agoVersion 2.2.7 releasedfrom the release logCommitted by tickera.
- 10 Oct 20169.5 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by Tickera for all 35 days we have observed it.
- It was last released 10 days ago (26 Aug 2026).
- Its author declares it tested up to WordPress 7.1, which is current.
- WordPress.org reports 2,000+ active installs.
- It carries 25 ratings, averaging 4.2 out of 5.
What we don’t know yet
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
Plugins that share this one’s tags and talk about the same things in their own descriptions. Distinctive tags count for far more than broad ones. Sharing hover means something, sharing woocommerce does not, and a plugin that never mentions the subject matter is left out however its author tagged it. Among close matches, more widely installed plugins are listed first. This is a grouping rather than a ranking of quality.
Page and Post Restriction
Restrict content access for WordPress (WP) | Restrict pages/posts in WP based on user roles and login status to protect content
1,000+ installs4.3★ (15)updated 25 Aug 2026
Compare side by side Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content
Protect your WordPress site, pages, posts, WooCommerce products, and categories with single or multiple passwords.
300,000+ installs4.4★ (139)updated 30 Jul 2026
150× the installs
Compare side by side Advanced Access Manager – Access Governance for WordPress
Access Governance for WordPress. Control roles, users, content, admin areas, and APIs to prevent broken access controls and excessive privileges.
100,000+ installs4.2★ (420)updated 25 May 2026
50× the installs
Compare side by side Intranet & Private Site – All-In-One Intranet
Turn WordPress into a private intranet in one click. Restrict access to logged-in members, with auto-logout and login redirect, also on multisite.
3,000+ installs5.0★ (11)updated 03 Aug 2026
Compare side by side HTTP Auth
Provides comprehensive security during development by protecting your entire site and your admin pages from brute-force attacks.
6,000+ installs4.2★ (6)updated 22 Jul 2025
Compare side by side Membership Plugin – Kadence Memberships
Kadence Memberships is a powerful WordPress membership plugin that gives you full control over who can and cannot view content on your WordPress site.
9,000+ installs3.1★ (99)updated 03 Sep 2026
Compare side by side Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about Restrict – membership, site, content and user access restrictions for WordPress: a person reads every submission, and corrections get a reply within 5 business days.