Field groups troubleshooting and FAQ

Last updated Oct 3, 20265 min read

My field group does not show on the edit screen

Work through this list in order:

Is it Active? Open the group, Settings › Group settings › Active. See Group settings.
Does it have a rule? A group without rules is shown nowhere. See Location rules.
Does every rule in one rule group fit the screen? A rule group is AND: Post type plus User role can never both be true. Put them in separate rule groups.
Status and terms. Rules read the saved state. On Add New the status is auto-draft; categories and terms chosen but not yet saved are not seen. Save, then reload.
Was the group saved after you added the first rule? The table needs mid/mtype columns; they are added on that save. If the group table lacks them the group is not shown. Open the group and click Save changes.
Is the screen supported? Terms: the edit screen (not Add New). Menu items: not supported yet. See Where field groups appear.
Is the table there? The list shows No table if not. See Table health.

Values are not saved

Check	Detail
`Custom fields were not saved: the form sent more values than the server accepts (max_input_vars = N)`	A large repeater exceeded PHP's `max_input_vars`. Raise it (try 3000 or more) or remove rows.
Settings › Health shows a database error	A column was dropped or altered outside the plugin. Repair it in Table health.
The group is registered in PHP	Its edit-screen values still save; only its definition is read-only in the editor.
The user cannot edit the post	Values are only saved when the person can edit the post.
A required field is empty	The values are saved, but `Saved, but these required fields are empty: ...` appears. Fill the field.

Saving the field group fails

Message	Fix
`The database rejected the change to "x": ... Nothing was changed.`	The database refused part of the change (duplicates for a unique index, values that do not fit a smaller column, an index that is too long). The table was rolled back. Correct the data or the setting.
`Database changes for this field group are still being applied. Save again when they are done.`	A background change runs. Wait for the Updating badge to clear.
`This field group is registered in PHP code. Change it in the code that registers it.`	The group comes from `wpmcf_register_field_group()`.
`Field key "x" cannot contain two underscores in a row.`	Rename the field key. Backup columns such as `price__bak` use `__` on purpose.
`Some new fields use the name of a column that still holds data from a removed field. Choose what to do with that data.`	The dialog These names hold saved values appears. See Changing a field group safely.
`Field group has 101 columns. Maximum allowed is 100.`	Move fields into a Group field.
`Field "x": the Gallery field type is not included in your plan.`	The type needs Pro.
`Field "x": add at least one choice.`	A Select, Radio, Checkbox or Button group has no choices.

The background change never finishes

The change is an Action Scheduler job (hook wpmcf/fields/schema_change). Check Tools › Scheduled Actions for pending or failed actions, and make sure WP-Cron runs (or a real cron calls wp-cron.php). After 15 minutes of no progress the editor treats it as interrupted; review Table health, then save again. A queued change can be cancelled with DELETE /wpmcf/v1/field-groups/{key}/schema-job.

Known limitations of this version

These are real behaviors in the current release. They are listed so you can work around them.

Area	Limitation	Workaround
Menu and Menu item rules	Rules can be saved but the menu editor does not show fields.	Read and write the values from code.
Location operator	An unknown operator sent through the REST API is stored as `equal`.	Use `equal` or `not_equal`.
Validation	Min length and Step are browser checks only.	Check them in your own code.
Field group list	No table / Healthy use remembered state.	Open the group to refresh.
Import as fields	The type is only a guess (SQL `text` becomes Text area, `varchar(254)` Email, `json` Group).	Change the type in the editor afterwards.

FAQ

Can I rename the group key? No. The key is the table name. Create a new group with the right key and move the data with SQL, or export and re-import (see Import and export).

Where is my data? In {prefix}wpmcf_fg_{group key}. It is not in wp_postmeta. Open it with phpMyAdmin or run SQL. See Overview.

Do themes that call get_post_meta() still work? Yes, when Bridge get_post_meta() and update_post_meta() is on (default). See Group settings.

Can I use my own SQL? Yes. Tables are normal InnoDB tables. Join on mid and mtype. Do not alter columns that fields use directly; use the editor, or fix drift with Table health.

What happens to values when I delete a field? Nothing; the column stays as a leftover column. See Changing a field group safely.

What happens to values when I delete a post? Permanent deletion removes the row; the Trash keeps it.

How many fields can a group have? 100 columns. Bundle related values in a Group field.

Is there an undo for a type change? The backup column {key}__bak holds the old values. There is no automatic undo.

Does it work with the block editor? Yes. Groups appear as meta boxes. Required fields lock the Update button until filled.

Do I need Pro? No for everything on these pages, except advanced field types, WooCommerce order rules and per-field translation modes (Business). See Overview.

How do I show a field on the front end? Use wpmcf_the_field(), wpmcf_get_field() or the [wpmcf_field] shortcode. See Developer API.

Still stuck?

Open WPM Fields › Settings › Health to read logged errors, and check Table health. Include the exact message when you contact support.

Was this page helpful?

Still stuck? Contact support