LIST MORE CUSTOM FIELD NAMES
List More Custom Field Names compatibility with REEID Translate
List More Custom Field Names compatibility with REEID Translate is being evaluated from available plugin evidence. Increases the number of custom field names/keys shown in the admin dropdown “Name” field when writing/editing posts and pages (default: 200 vs WordPress default: 30). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for List More Custom Field Names.
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
List More Custom Field Names is documented in the Other category with 6 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 List More Custom Field Names 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
- Increases the number of custom field names/keys shown in the admin dropdown “Name” field when writing/editing posts and pages (default: 200 vs WordPress default: 30).
- Provides two configuration mechanisms to change the custom field names limit: a `CUSTOM_FIELD_NAMES_LIMIT` constant in `wp-config.php`, or a `c2c_list_more_custom_field_names` filter hook.
- Uses precedence rules for limit configuration: if the `CUSTOM_FIELD_NAMES_LIMIT` constant is defined and truthy, it takes precedence over the `c2c_list_more_custom_field_names` filter.
- Validates configured/filtered limit values: if the configured/returned value is not an integer (or integer string), the plugin falls back to its default.
- Affects only the dropdown listing count; it does not change which custom field keys are eligible beyond what WordPress already does (e.g., private custom field keys remain hidden).
- Requires the configured limit to be at least the WordPress default of 30 (per documentation).
CONTENT BOUNDARY
List More Custom Field Names 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
List More Custom Field Names and REEID Translate FAQ.
What does List More Custom Field Names do according to the available plugin evidence?
List More Custom Field Names has 6 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 List More Custom Field Names?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for List More Custom Field Names?
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 List More Custom Field Names in a multilingual WordPress workflow.
REEID documents List More Custom Field Names 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.