RAPTOR SCHEDULED CONTENT EXPIRY
Raptor Scheduled Content Expiry compatibility with REEID Translate
Raptor Scheduled Content Expiry compatibility with REEID Translate is being evaluated from available plugin evidence. Scheduled content expiry for posts, pages, public custom post types, and WooCommerce products No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Raptor Scheduled Content Expiry.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Raptor Scheduled Content Expiry is documented in the Other category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Raptor Scheduled Content Expiry compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Scheduled content expiry for posts, pages, public custom post types, and WooCommerce products
- Configurable expiry actions including move to draft, 301/302 redirect, content swap, or hide from archive/search
- Role-based access control restricting management to Administrators and Editors
- Audit log tracking expiry events with timestamps, actions taken, and user attribution
- Bulk Edit and Quick Edit support for managing expiry dates across multiple items
- Timezone-aware scheduling integrated with WordPress timezone settings
- Dashboard widget displaying upcoming expirations within the next seven days
- Caching compatibility via smcexp_cache_purge action hook for cache invalidation
CONTENT BOUNDARY
Raptor Scheduled Content Expiry capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Raptor Scheduled Content Expiry and REEID Translate FAQ.
What does Raptor Scheduled Content Expiry do according to the available plugin evidence?
Raptor Scheduled Content Expiry has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Raptor Scheduled Content Expiry?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Raptor Scheduled Content Expiry?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Raptor Scheduled Content Expiry in a multilingual WordPress workflow.
REEID documents Raptor Scheduled Content Expiry functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.