Meta Box AIO Fields

Meta Box AIO is a developer-oriented custom field framework for WordPress that supports over forty field types and offers both a code-based API and a visual UI builder through its extensions. WPfaker provides a dedicated Meta Box AIO adapter that detects every Meta Box AIO field group on your site and generates realistic, correctly formatted data for each field type. Whether you use Meta Box AIO's code API with rwmb_meta_boxes filter, the MB Custom Post Type extension, or the visual Meta Box Builder UI, WPfaker reads your field definitions and fills them automatically.

Where Meta Box AIO differs from other field plugins is in its approach to repeatable content. Instead of a dedicated repeater field type, Meta Box AIO uses a clone flag that can be applied to any field — turning a simple text field into a repeatable text field, or a group into a repeatable group. WPfaker handles this cloneable pattern natively, generating the correct array structure for both single and cloned fields.

TIP

Meta Box AIO support works alongside other field plugins. If your site also uses ACF or JetEngine, all plugins are detected simultaneously and their fields are populated in a single generation run. See Custom Fields for the general overview of multi-plugin support.

Supported Field Types

WPfaker supports approximately forty Meta Box AIO field types. Each type is detected automatically when you select a post type that has Meta Box AIO field groups assigned to it. No manual mapping or configuration is required.

Text Fields

The text field generates words or short sentences, with the output influenced by field name analysis through WPfaker's Field Detection system. A text field named customer_email produces an email address, while one named notes produces a short sentence. The url field produces a realistic website URL. The email field generates a safe, non-deliverable email address. The password field generates a random string between 8 and 16 characters. The hidden field produces an MD5 hash string, suitable for system-generated values that are not displayed to users.

Content Fields

The textarea field generates multiple paragraphs of lorem ipsum text, suitable for description areas and longer free-text inputs. The wysiwyg field produces rich HTML content with paragraphs, headings, and formatting. The oembed field generates a video embed URL from popular providers like YouTube and Vimeo. The custom_html field produces a wrapped HTML block with paragraph content.

Numeric Fields

The number field generates random integers or decimals. When the field has configured min and max bounds, WPfaker respects those constraints. Field name analysis further refines the output — a number field named price produces a currency-formatted value, while one named bedrooms produces a small integer. The range and slider fields work similarly, always generating a value within the configured bounds.

Selection Fields

The select and select_advanced fields pick a random option from the choices defined in the field configuration. Select advanced adds search functionality in the admin UI, but both store data identically. The radio field picks exactly one option. The checkbox field (single) produces a boolean 1 or 0 value, acting as an on/off toggle. The checkbox_list field selects a random subset of available options. The button_group field picks one option from the configured buttons. The autocomplete field selects one to three options from the available choices. The image_select field picks a random option from the visual image choices. The switch field produces a random boolean value.

INFO

Meta Box AIO's single checkbox field type is a toggle (on/off), not a multi-select. For multi-select checkboxes, Meta Box AIO uses checkbox_list. WPfaker handles both correctly — checkbox returns 1 or 0, while checkbox_list returns an array of selected values.

Date and Time Fields

The date field generates a random date in Y-m-d format. The datetime field generates a combined date and time in Y-m-d H:i:s format. The time field generates a random time in H:i:s format. All generated dates fall within a reasonable range to produce plausible content. Field name analysis applies here too — a date field named birthday generates a date further in the past than one named event_date.

Color Fields

The color field generates a random hex color value such as #44CEFF. Colors are generated using FakerPHP's color provider for a wide range of results.

File and Media Fields

Meta Box AIO offers several file and media field types, and WPfaker handles each one with the correct storage format.

The file, file_advanced, and file_upload fields store file attachment IDs. WPfaker selects from existing media library attachments. The file_input field stores a URL string rather than an attachment ID.

The image, image_upload, and image_advanced fields store arrays of image attachment IDs, with the count limited by the field's max_file_uploads setting. The single_image field stores a single attachment ID. The video field stores a structured array with src (video URL) and type properties.

Relational Fields

The post field references posts of another post type. Because the referenced posts may not exist at the time of generation, WPfaker defers these fields to the second pass of its three-pass system. The taxonomy and taxonomy_advanced fields reference taxonomy terms. The user field references WordPress users by ID.

Map Fields

The map field (Google Maps) and osm field (OpenStreetMap) both store location data as a comma-separated "lat,lng,zoom" string. WPfaker generates random geographic coordinates with a default zoom level of 14.

"40.7128,-74.0060,14"

INFO

Meta Box AIO's map storage format is unique — a single string with comma-separated values, not a JSON object. WPfaker writes in this exact format so that Meta Box AIO's map rendering functions display the marker correctly.

Special Fields

The key_value field stores an array of key-value pair objects. WPfaker generates two to four pairs, each with a random word as the key and a short sentence as the value.

[
  { "key": "color", "value": "Deep ocean blue with subtle gradient" },
  { "key": "material", "value": "Brushed aluminum with matte finish" }
]

The fieldset_text and text_list fields store multiple named text inputs as an associative array, with the field's configured options as keys. The background field stores CSS background properties as a structured array with color, image, repeat, position, attachment, and size keys. The sidebar field returns a registered WordPress sidebar ID.

Layout Fields

Meta Box AIO includes field types that serve purely visual purposes in the admin editor and store no data. WPfaker recognizes and skips these automatically during generation:

• The heading field displays a section title in the editor.
• The divider field displays a horizontal separator line.
• The tab field groups other fields into tabbed sections.

Cloneable Fields (Repeater Pattern)

Meta Box AIO does not have a dedicated repeater field type. Instead, any field can be made repeatable by setting clone: true in the field configuration. WPfaker detects this flag and generates an array of values instead of a single value.

// Meta Box AIO field definition
[
    'id'    => 'phone_numbers',
    'type'  => 'text',
    'name'  => 'Phone Numbers',
    'clone' => true,
    'max_clone' => 5,
]

When WPfaker encounters a cloneable field, it generates between one and three cloned values (up to the max_clone limit). Each clone receives its own independently generated value based on the field type and name detection.

For example, a cloneable text field named phone_numbers with max_clone: 5 might produce:

["+1 (555) 234-5678", "+1 (555) 876-5432", "+1 (555) 345-6789"]

TIP

The max_clone setting in Meta Box AIO limits how many clones the admin editor allows. WPfaker respects this limit and never generates more clones than max_clone permits.

Group Fields

Meta Box AIO's group field type contains sub-fields and stores their values as an associative array. WPfaker generates values for every sub-field within the group, skipping any layout-only sub-fields (heading, divider, tab).

// Meta Box AIO group field definition
[
    'id'     => 'team_member',
    'type'   => 'group',
    'name'   => 'Team Member',
    'fields' => [
        ['id' => 'name',  'type' => 'text'],
        ['id' => 'role',  'type' => 'text'],
        ['id' => 'email', 'type' => 'email'],
    ],
]

WPfaker produces a structured array:

{
  "name": "Sarah Johnson",
  "role": "Lead Developer",
  "email": "sarah.johnson@example.com"
}

Groups can also be cloneable. When a group has clone: true, WPfaker generates multiple group instances, each with independently generated sub-field values.

Detection Mechanism

WPfaker detects Meta Box AIO through two checks. First, it looks for the RWMB_Loader class, which is present when Meta Box AIO is loaded. Second, it checks for the RWMB_VER constant, which Meta Box AIO defines at initialization. If either is present, the Meta Box AIO adapter activates. WPfaker additionally checks for the MB_AIO class and the MetaBox\AIO\Loader class.

Meta Box AIO registers custom post types through the MB Custom Post Type extension, storing CPT definitions as mb-post-type posts. WPfaker reads these registrations and includes them in the post type dropdown alongside CPTs from other sources.

Data Storage

Meta Box AIO stores field values using WordPress's standard wp_postmeta table. WPfaker saves generated values through Meta Box AIO's rwmb_set_meta() function when available, falling back to WordPress's update_post_meta() if needed. This ensures compatibility with Meta Box AIO's data retrieval functions (rwmb_meta(), rwmb_get_value()) and any front-end rendering that depends on them.

Smart Field Name Detection

Beyond standard field type handling, WPfaker's Field Detection system analyzes Meta Box AIO field names to generate contextually appropriate data. For text-based fields (text, textarea, number, range, slider), the field name is evaluated against over 780 built-in patterns across 160 detection types before falling back to generic generation.

A number field named monthly_revenue receives a realistic currency value like 12450.00. A text field named phone receives a locale-formatted phone number. When neither the field type nor the name produces a match, AI Detection can be enabled for semantic analysis.

Troubleshooting

If Meta Box AIO fields are not being detected, confirm that Meta Box AIO is active and that the meta box is assigned to the correct post type. Fields using layout-only types (heading, divider, tab) are expected to be skipped. If cloneable fields produce unexpected output, verify that the max_clone value is set correctly in your field definition.

For Meta Box AIO, ensure that the AIO plugin is activated and that the extensions you need (MB Custom Post Type, MB Relationships, etc.) are enabled in the AIO settings panel.

If map fields display incorrectly on the frontend, verify that the stored format matches Meta Box AIO's expected "lat,lng,zoom" string format. WPfaker writes in this format by default, but if the field was previously populated with a different format, the rendering may be inconsistent.

INFO

For general custom field troubleshooting that applies across all field plugins, see the Custom Fields page.