ATSHIFT USER PROFILE FIELDS
atshift User Profile Fields compatibility with REEID Translate
atshift User Profile Fields compatibility with REEID Translate is being evaluated from available plugin evidence. Creates custom user profile fields and manages their visibility on WordPress user profile screens. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for atshift User Profile Fields.
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
atshift User Profile Fields 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 atshift User Profile Fields 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
- Creates custom user profile fields and manages their visibility on WordPress user profile screens.
- Supports required-field validation for configured custom profile fields.
- Provides multiple custom field types including select, radio, checkbox, text, textarea, email, URL, and number fields.
- Stores custom field values as user meta using the meta key prefix `_atshift_upf_` followed by the configured field key.
- Includes default WordPress profile field visibility controls to hide unnecessary default profile fields.
- Offers downloadable JSON distribution sets and validated file import for field configurations.
- Includes a bundled WordPress default profile preset used for user creation and saved-user editing.
- Optionally integrates passkey field placement when used alongside atshift Freeform Login (for passkey management).
CONTENT BOUNDARY
atshift User Profile Fields 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
atshift User Profile Fields and REEID Translate FAQ.
What does atshift User Profile Fields do according to the available plugin evidence?
atshift User Profile Fields 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 atshift User Profile Fields?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for atshift User Profile Fields?
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 atshift User Profile Fields in a multilingual WordPress workflow.
REEID documents atshift User Profile Fields 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.