ATSHIFT FIELDS (MAINTENANCE FOR CUSTOM FIELD SUITE)
atshift Fields (Maintenance for Custom Field Suite) translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what atshift Fields (Maintenance for Custom Field Suite) does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Security hardening for known Custom Field Suite (CFS) 2.6.7 vulnerability classes, including Loop field code execution, Term field SQL injection, stored XSS in CFS form title/content, and missing post-update capability checks via CFS forms.
- Front-end User fields are blocked at rendering, validation, and saving boundaries (values are omitted from front-end forms and ignored if submitted directly).
- Save/Publish behavior includes a protection to prevent scheduled posts from becoming public when an editor without the post type’s publish capability submits a past publication date.
- Field input handling includes inline validation messages and an error summary that opens the containing Tab/Loop/Accordion group and scrolls to the selected invalid field.
- Native WordPress fields (e.g., Post Title, Post Content, Save/Publish, Categories/Tags, Featured Image) are edited directly as native objects rather than as CFS-only post meta fields.
- Provides format validation for certain field types (Phone Number, Email Address, Number, URL, and Time fields with hour/minute select menus).
Distinctive features
Security hardening for known Custom Field Suite (CFS) 2.6.7 vulnerability classes, including Loop field code execution, Term field SQL injection, stored XSS in CFS form title/content, and missing post-update capability checks via CFS forms. Front-end User fields are blocked at rendering, validation, and saving boundaries (values are omitted from front-end forms and ignored if submitted directly). Save/Publish behavior includes a protection to prevent scheduled posts from becoming public when an editor without the post type’s publish capability submits a past publication date. Field input handling includes inline validation messages and an error summary that opens the containing Tab/Loop/Accordion group and scrolls to the selected invalid field. Native WordPress fields (e.g., Post Title, Post Content, Save/Publish, Categories/Tags, Featured Image) are edited directly as native objects rather than as CFS-only post meta fields. Provides format validation for certain field types (Phone Number, Email Address, Number, URL, and Time fields with hour/minute select menus).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what atshift Fields (Maintenance for Custom Field Suite) does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
atshift Fields (Maintenance for Custom Field Suite) and REEID Translate FAQ.
Does the current evidence establish translation scope for atshift Fields (Maintenance for Custom Field Suite)?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.