Two field types — Password and Gallery — are no longer offered when you add a new field. Password fields already in a group keep working normally. Gallery fields do not, and need attention before anyone edits a post that has one.
What It Does
These types are not in the field type list in Nexter Extension 4.9.0; they appear only as Password (legacy) and Gallery (legacy) on fields that already use them. A Password field still renders and saves exactly as before. A Gallery field does not: the editor has no control for it any more, so it falls back to a single plain text box, and saving the post replaces the stored attachment IDs with an empty value.
Before You Start
- You are looking at a field group created in an earlier version of Nexter.
- A field shows a type you cannot select when adding a new field.
What to Do Instead
- For a Password field, use a Text field — and do not store real credentials in post meta, which is readable by anyone who can edit the post.
- For a Gallery field, use a Repeater with a single Image sub-field. That gives editors the same add-reorder-remove behaviour, with the row order under their control.
- Migrate values with a one-off script if you need the old data in the new shape. Nothing migrates automatically.
Limitations
- Neither type can be selected for a new field.
- Password values are untouched and are still returned by the field API.
- Gallery values are not safe to leave alone. The field renders as a plain text box, so the next time anyone saves that post the stored attachment IDs are lost. Copy the values out before editing the post.
- There is no automatic migration from Gallery to a Repeater. The stored shapes differ.
Troubleshooting
I cannot find Password or Gallery in the field type list
They are not selectable for new fields in Nexter Extension 4.9.0. Use the replacements above.
An old gallery field shows a plain text box
That is the fallback for a type the editor can no longer draw, and it is destructive: the value behind it is a list of attachment IDs that a single text box cannot hold. Do not save the post. Read the values first with nxt_field_value_raw(), create a Repeater with an Image sub-field, write the IDs across, then remove the old field.
