--- title: "Legacy Field Types in Nexter Fields" url: https://nexterwp.com/docs/nexter-fields-legacy-field-types/ date: 2026-09-21 modified: 2026-11-12 lang: en author: "Aditya Sharma" description: "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..." image: https://nexterwp.com/wp-content/uploads/2026/09/nexter-fields-legacy-field-types-1024x519.jpg word_count: 400 --- # Legacy Field Types in Nexter Fields ## Key Takeaways - Nexter Extension 4.9.0 no longer offers Password and Gallery as new field types, and existing fields appear only as Password (legacy) and Gallery (legacy). - Password fields still render and save exactly as before, but the post meta is readable by anyone who can edit the post, so the replacement is a Text field. - Gallery fields fall back to a single plain text box, and saving the post replaces the stored attachment IDs with an empty value; the replacement is a Repeater with a single Image sub-field. 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. ![The Field Type dropdown, which no longer lists Password or Gallery](https://nexterwp.com/wp-content/uploads/2026/09/nxt-fields-h-shared-field-type.webp) - 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. ## Related Docs - [Repeater field](https://nexterwp.com/docs/wordpress-repeater-field/)- [Image field](https://nexterwp.com/docs/wordpress-image-field/)- [Text field](https://nexterwp.com/docs/wordpress-text-field/) ## Frequently Asked Questions **Q: Why did my old Gallery field turn into a plain text box in Nexter Fields?** A: That fallback happens because Gallery is a legacy type in Nexter Extension 4.9.0 and the editor can no longer draw its normal control. The stored value behind it is a list of attachment IDs, which a single text box cannot represent safely. The practical risk is data loss on save, so the post should not be saved until the values are copied out and moved into a new structure. **Q: What should I use instead of a legacy Password field in Nexter Fields?** A: A Text field is the replacement for Password in Nexter Fields. The key reason is that Password fields already in a group still render and save normally, but new ones are no longer offered. One important caution from the page is that real credentials should not be stored in post meta, because anyone who can edit the post can read it. **Q: How do I replace a legacy Gallery field without losing image order?** A: A Repeater with a single Image sub-field is the intended replacement. That setup preserves the add, reorder, and remove workflow editors expect, while keeping row order under their control. The page also notes that nothing migrates automatically, so if you need the old data in the new shape, plan for a one-off script instead of assuming Nexter will convert it for you. **Q: Can I still use old Password and Gallery fields in an existing field group?** A: Password fields already in a group keep working normally, but Gallery fields do not stay safe to leave alone. In Nexter Extension 4.9.0 they appear only as legacy types on existing fields, not as choices for new ones. That means Password can keep returning values through the field API, while Gallery needs attention before anyone edits the post. **Q: What happens if someone saves a post with an old Gallery field?** A: Saving that post replaces the stored attachment IDs with an empty value. The editor falls back to a plain text box because it cannot render the old Gallery control anymore, and that text box cannot hold the original structured value safely. The page’s warning is blunt: copy the values out before editing, or read them first with `nxt_field_value_raw()`. **Q: How do I migrate legacy Gallery values to a Repeater field?** A: The migration path is to read the old values first with `nxt_field_value_raw()`, create a Repeater with an Image sub-field, write the attachment IDs across, and then remove the old field. That matters because Gallery and Repeater store different shapes, so there is no automatic migration from one to the other. [Repeater field](https://nexterwp.com/docs/wordpress-repeater-field/) and [Image field](https://nexterwp.com/docs/wordpress-image-field/) are the relevant building blocks.