
C3 CLOUDFRONT CACHE CONTROLLER
C3 Cloudfront Cache Controller compatibility with REEID Translate
C3 Cloudfront Cache Controller compatibility with REEID Translate is being reviewed using official plugin documentation. Clears (invalidates) CloudFront cache when posts are published, by sending invalidation requests to the CloudFront Invalidation API. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What C3 Cloudfront Cache Controller 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
C3 Cloudfront Cache Controller is documented in the Performance category with 7 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 C3 Cloudfront Cache Controller 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
- Clears (invalidates) CloudFront cache when posts are published, by sending invalidation requests to the CloudFront Invalidation API.
- Sends invalidation for specific URL targets: the TOP page URL, the published post page URL, and the category archive page URL.
- Supports device/viewer detection via CloudFront headers using wp_is_mobile(), including support for HTTP_CLOUDFRONT_IS_MOBILE_VIEWER and HTTP_CLOUDFRONT_IS_TABLET_VIEWER.
- Mitigates CloudFront caching for preview pages by adding a post_date query parameter and by setting a cookie named wordpress_loginuser_last_visit for logged-in preview behavior.
- Removes the wordpress_loginuser_last_visit cookie when the user signs out/logs out from the Dashboard.
- Provides configuration via environment variables/defines for AWS credentials and the CloudFront distribution ID (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, C3_DISTRIBUTION_ID).
- Uses a custom AWS CloudFront implementation (instead of the official AWS SDK) to reduce dependencies and improve performance.
TRANSLATION BOUNDARY
C3 Cloudfront Cache Controller 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
C3 Cloudfront Cache Controller and REEID Translate FAQ.
What does C3 Cloudfront Cache Controller do?
C3 Cloudfront Cache Controller has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does C3 Cloudfront Cache Controller 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 C3 Cloudfront Cache Controller?
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 C3 Cloudfront Cache Controller in a multilingual WordPress workflow.
REEID documents C3 Cloudfront Cache Controller 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.