Census › Plugin profiles › Schedule Post Changes With PublishPress Future
Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories
Figures from the Plugin Directory Census · as of 28 Aug 2026
100,000
Active installs, lower bound
Group: 100,000 to 999,999 installs
9
Days since the last release
Group median: 12
4.5
out of 5, from 171 ratings
Group median: 4.7 (10+ ratings)
80.0%
Support threads marked resolved, two months
Group: 68.2%
Full profile on wordpress.orgShow on the mapCompare with your own plugins
What is Schedule Post Changes With PublishPress Future and who is behind it?
Schedule Post Changes With PublishPress Future is a WordPress plugin by PublishPress. It has been listed in the directory since 31 Jul 2008, so for 18 years. PublishPress has 6 plugins with at least 10,000 installs in the census. With 100,000 to 199,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 9 days before the reference date, and it is tested up to WordPress 7.1.
This is how the author describes the plugin on wordpress.org:
“PublishPress Future can make scheduled changes to your content. You can unpublish posts, move posts to a new status, update the categories, and more.”
Self-description on wordpress.org, retrieved on 10 Sept 2026
When was Schedule Post Changes With PublishPress Future last released?
The last release of Schedule Post Changes With PublishPress Future came 9 days before the reference date; the group median is 12 days.
How many installs does Schedule Post Changes With PublishPress Future have?
Schedule Post Changes With PublishPress Future had 100,000 to 199,999 active installs on the reference date. Within its group, 219 plugins had a higher band and 179 plugins the same band.
The API reports installs only as a lower bound with one significant figure: 100,000 means at least 100,000 and at most 199,999.
Which WordPress version is Schedule Post Changes With PublishPress Future tested with?
No directory notice: tested up to WordPress 7.1, while core stood at 7.1 on the reference date. The notice appears once the field falls below 6.9; that applied to 8.0% of the group.
How does Schedule Post Changes With PublishPress Future compare with its group?
The group holds 399 listed plugins. 36.1% of them had a more recent last release than Schedule Post Changes With PublishPress Future; 5.3% had no release for more than 365 days.
| Figure | Schedule Post Changes With PublishPress Future | Group, 399 plugins |
|---|---|---|
| Days since the last release | 9 | median 12 |
| Rating | 4.5 (171) | median 4.7 (10+ ratings) |
| Support threads marked resolved | 80.0% | 68.2% |
| Tested up to | 7.1 | 47.6% on 7.1 |
| Requires PHP | 7.4 | most often 7.4 (41.6%) |
All values on the reference date
| Slug | post-expirator |
|---|---|
| Author | PublishPress |
| Active installs | 100,000 to 199,999 |
| Last release | 9 days before the reference date |
| Tested up to | WordPress 7.1 · core on the reference date: 7.1 |
| Requires WordPress | 6.7 |
| Requires PHP | 7.4 |
| Rating | 4.5 out of 5 from 171 ratings |
| Support threads, two months | 4 of 5 marked resolved |
| Listed since | 31 Jul 2008 |
| Total downloads | 4,346,495, updates included |
| Tags | automatic-changes, schedule-changes, unpublish-posts, update-posts, workflows |
Tags
| Tag | Plugins with 10,000+ installs and this tag | Rank by installs | Median days since release |
|---|---|---|---|
| automatic-changes | 1 | 1 | 9 |
| schedule-changes | 1 | 1 | 9 |
| unpublish-posts | 1 | 1 | 9 |
| update-posts | 1 | 1 | 9 |
| workflows | 2 | 2 | 15 |
Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.
Class of 2008
Schedule Post Changes With PublishPress Future has been listed since 31 Jul 2008. Of the 45 plugins with 10,000+ installs added in 2008, 71.1% released within the 365 days before the reference date.
Same group, shared tags
Not a recommendation; the same figures for comparison. Alphabetical.
| Plugin | Active installs | Last release | Rating |
|---|---|---|---|
| Mailchimp for WooCommerce | 200,000 to 299,999 | 21 days before the reference date | 4.0 (725) |
Do you maintain Schedule Post Changes With PublishPress Future?
If you maintain Schedule Post Changes With PublishPress Future, you can link to this profile, for example from your readme or your website. Both snippets show this badge:
HTML
<a href="https://hafenstudios.com/en/census/plugins/post-expirator/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="Schedule Post Changes With PublishPress Future in the Plugin Directory Census 01/2026" width="220" height="40"></a>
Markdown
[](https://hafenstudios.com/en/census/plugins/post-expirator/)
The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.
A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.
How to cite
hafenstudios (2026): Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/post-expirator/
Source and status
All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.
Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.
