TEYDEA CONTENT EXPIRY
Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes compatibility with REEID Translate
Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes compatibility with REEID Translate is being reviewed using official plugin documentation. Automatically changes post status to draft, private, or trash upon expiry No specific text shown to visitors is currently confirmed for translation.
Visit Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes ↗
AWAITING VERIFICATION
What Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes is documented in the Other category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Automatically changes post status to draft, private, or trash upon expiry
- Integrates with Block Editor (Gutenberg) and Classic Editor for expiry configuration
- Supports posts, pages, and public custom post types
- Provides email notifications for pre-expiry warnings and post-expiry events
- Includes frontend blocks and shortcodes for countdown timers and timed content visibility
- Offers admin dashboard widgets, list columns, and bulk/quick edit capabilities for managing expiring content
TRANSLATION BOUNDARY
Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes and REEID Translate FAQ.
What does Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes do?
Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes in a multilingual WordPress workflow.
REEID documents Teydea Content Expiry – Auto-Expire Posts & Scheduled Status Changes functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.