Teydea Content Expiry - Auto-Expire Posts & Scheduled Status Changes
| 开发者 |
teydeastudio
bartoszgadomski |
|---|---|
| 更新时间 | 2026年10月30日 18:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
详情介绍:
- Automatically move expired content to draft, private, or trash - no manual cleanup needed.
- Get notified by email before and after content expires, so nothing slips through the cracks.
- Show visitors countdown timers and timed content blocks that respond to expiry dates.
- Manage expiring content at scale with bulk edit, quick edit, and a dashboard widget.
安装:
- Upload the
stalepilotdirectory to/wp-content/plugins/, or install it directly through the WordPress plugin screen. - Activate the plugin through the "Plugins" screen in WordPress.
- Go to Settings > Content Expiry to choose which post types support expiry and configure default actions and notifications.
- Edit any post or page and use the "Content Expiry" panel in the sidebar to set an expiry date and action.
屏幕截图:
常见问题:
Which post types are supported?
By default, Teydea Content Expiry is enabled for posts and pages. You can enable it for any public custom post type in the plugin settings under Settings > Content Expiry.
What happens when a post expires?
The plugin performs the action you selected for that post: it moves the post to draft, makes it private, or moves it to trash. You can set a default action in the settings and override it per post.
Can I undo an automated expiry?
Yes. In the classic posts or pages list, hover over an expired post and choose Restore previous status. For posts expired into Trash, open the Trash view first. The action appears when a valid previous status was recorded and you have permission to restore it. Making a post private removes its password, so a post that expired into Private is not restored to Published or Scheduled if it may have had a password. The Expiry column says so; publish the post manually and set its password again. A successful restore clears the expiry record, date, action, and pending expiry schedule. Set a new expiry if you want the content to expire again. The action is available in the classic list tables; it is not available in the block-editor sidebar or Site Editor DataViews.
Can I display a countdown timer on the front end?
Yes. The plugin includes an Expiry Countdown block (and a [stalepilot_countdown] shortcode) that displays either a live countdown timer or a static formatted date. You can customize colors, threshold warnings, and the expired message.
What happens if I restore a trashed post that had an expiry date?
If the expiry date is still in the future, the plugin automatically reschedules the expiry. If the expiry date has already passed, the stale expiry metadata is cleaned up.
Where can I find the unminified source code?
All source ships with the plugin: the plugin's own JavaScript is in src/, and the bundled @teydeastudio/components and @teydeastudio/utils libraries are in deps/js/components/src/ and deps/js/utils/src/. To rebuild, install Node.js 24 and run npm install && npm run build in the plugin directory.
更新日志:
- Editors can undo an automated expiry with a new "Restore previous status" action in the Posts and Pages lists, and the Expiry column shows the status a post had before it expired
- Fixed expiry dates set across a daylight saving change being stored an hour off
- Personal-data exports now include notification recipient memberships, and erasure requests remove the user from the recipients
- Accessibility: the Expires date field in the document sidebar and the Timed Content block now has a label
- A canceled scheduled action now stays canceled when it was already running
- Saving settings now reports an error when WordPress refuses the database write
- The minimum supported WordPress version is now 6.8
- Dependencies updated
- Code improvements
- Fixed roles and users past the tenth not being selectable in the settings
- Editor panel open/closed and enabled/disabled preferences are now remembered between page loads
- Dashboard widget table rows are now announced by screen readers with the post they belong to
- Dependencies updated
- Code improvements
- Plugin renamed to "Teydea Content Expiry", with a new icon and updated links
- Compatibility with WordPress 7.1 confirmed
- Fixed help text not being announced as the description of the field it belongs to on the settings and editor screens
- Fixed a successful settings save reporting itself as failed on WordPress 6.6
- Plugin banners and screenshots added to the WordPress.org listing
- Dependencies updated
- Code improvements
- Added the plugin icon
- Settings page tabs are now reflected in the URL, so a tab can be bookmarked and shared
- Added a clear admin notice for unmet server requirements (minimum PHP/WordPress version, required extensions)
- Dependencies updated
- Code improvements
- An FAQ entry added to readme.txt, explaining where the unminified source code lives in the plugin and how to rebuild it from source
- The "Pre-expiry warning" and "Dashboard widget window" settings now accept any number of days within a reasonable range, with quick-set presets for common values
- Direct loading of wp-includes/version.php in the WordPress version detection fallback removed
- The first stable release