Plugin profile · observed daily since 02 Aug 2026
DiaryPress
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 Tom throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
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.
Very early-stage: 90+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
4 downloads a day over the last 7 days, rising 36% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Install band rose to 90+ on 07 Aug 2026, from 70+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.
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 | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep | 07 Sep | 08 Sep | 09 Sep | 10 Sep | 11 Sep | 12 Sep | 13 Sep | 14 Sep | 15 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 19 | 0 | 0 | 11 | 0 |
Unchanged throughout: ratings total (5) · active installs (90+) · version (5.4) · support threads (0) · threads resolved (0)
45 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Is anyone still maintaining this?
- Last released 12 Apr 2025, 522 days ago.
- Declares compatibility only up to WordPress 6.8.8, while 7.1 is current. The author has not confirmed it runs on the last 3 releases.
- Tom publishes no other plugin in the directory, so there is no wider activity to compare against.
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.
- 05 Aug 20261 month agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20261 month agoInstall band moved to 60+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 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.
- 12 Apr 202517 months agoVersion 5.4 released
- 17 Aug 200917 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 Tom for all 45 days we have observed it.
- It was last released 17 months ago (12 Apr 2025).
- Its author declares it tested up to WordPress 6.8.8; WordPress is now on 7.1.
- WordPress.org reports 90+ active installs.
- It carries 5 ratings, averaging 2.0 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.
This plugin requires users to be logged in to view the website. Activate the plugin to enforce login, and deactivate it to remove the restriction.
Force visitors to log in before accessing your site with extensive exception controls.
Lock down your private WordPress site. Force login for all visitors, block REST API and XML-RPC, and lock out repeated failed login attempts.
Makes your wordpress blog private unless the user is logged in, optionally setting a minium user level. Modified from http://wordpress.
Makes a blog private or not accessable for a time period. Allows and dissallows registering also in WP Multiple Blogs. Shows your own login message.
Redirects non-logged users to the login page when they follow a link to a post, page, or cpt which is protected by post status.
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 DiaryPress: a person reads every submission, and corrections get a reply within 5 business days.