CUSTOM FIELD FOR WP JOB MANAGER
Custom Field For WP Job Manager compatibility with REEID Translate
Custom Field For WP Job Manager compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a field editor to add, edit, and manage custom job and company fields for WP Job Manager without coding. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Custom Field For WP Job Manager.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Custom Field For WP Job Manager is documented in the Forms category with 7 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 Custom Field For WP Job Manager 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
- Provides a field editor to add, edit, and manage custom job and company fields for WP Job Manager without coding.
- Uses the standard WP Job Manager filter `submit_job_form_fields` to integrate custom fields into job submission forms.
- Adds custom fields to the frontend job submission form via a “Form Customizer” tab in the WP Admin.
- Supports creating custom placeholders for fields and uses `{label}` and `{value}` placeholders for custom output on the listing page.
- Stores fields as a Custom Post Type (`wpjmcf`) and stores settings as post meta using the `_cfwjm` suffix.
- Includes a shortcode to display saved custom fields: `[cm_fieldshow key="_field_cfwjm13" job_id="123"]`.
- Supports a “File” field type that allows users to upload documents through the frontend form.
CONTENT BOUNDARY
Custom Field For WP Job Manager 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
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
Custom Field For WP Job Manager and REEID Translate FAQ.
What does Custom Field For WP Job Manager do according to the available plugin evidence?
Custom Field For WP Job Manager has 7 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 Custom Field For WP Job Manager?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Custom Field For WP Job Manager?
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 Custom Field For WP Job Manager in a multilingual WordPress workflow.
REEID documents Custom Field For WP Job Manager 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.