---
title: "Field Group Changes on Disk Not Showing in WordPress"
url: https://nexterwp.com/docs/field-group-changes-not-showing-cache/
date: 2026-09-14
modified: 2026-11-12
lang: en
author: "Aditya Sharma"
description: "You edited a field group definition on the server — a deploy, a file copy — and the site carries on serving the old version. This is a caching behaviour,..."
image: https://nexterwp.com/wp-content/uploads/2026/09/field-group-changes-not-showing-cache-1024x519.jpg
word_count: 285
---

# Field Group Changes on Disk Not Showing in WordPress

## Key Takeaways

- Nexter stores field group definitions as files and keeps a cached model, so a change made outside the admin can keep serving the old version.
- Clearing only the transient is not enough; the post says to delete wp option delete nxt_model_cache first, then wp transient delete nxt_ct_definitions_v1.
- Editing definitions in the admin invalidates the cache correctly, while changes made directly on the server need both caches cleared and may also need a page cache or CDN purge.

You edited a field group definition on the server — a deploy, a file copy — and the site carries on serving the old version. This is a caching behaviour, and it needs two caches cleared, not one.

## What It Does

Nexter stores field group definitions as files and keeps a cached model so every page load does not rescan them. The cache is keyed on the index file rather than on the definition contents, so a change made outside the admin can go unnoticed.

## Before You Start

- You changed a definition file directly on the server.- You have WP-CLI access, or can delete options and transients another way.

## Clear Both Layers

- Clear the model cache option: `wp option delete nxt_model_cache`

- Clear the definitions transient: `wp transient delete nxt_ct_definitions_v1`

- Reload the page and confirm the change is live.

![A field group open in the builder](https://nexterwp.com/wp-content/uploads/2026/09/nxt-fields-h-shared-add-field.webp)

- If you use a page cache or a CDN, purge that too — it can hold the old rendered output independently.

## Display the Value

Both commands, in the order that works:

`wp option delete nxt_model_cache
wp transient delete nxt_ct_definitions_v1`

## Limitations

- **Clearing only the transient is not enough.** It simply repopulates from the still-stale option. Both have to go, in that order.- Editing definitions in the admin invalidates the cache correctly. This only affects changes made outside it.- The cached model lives in a `wp_options` row, so it survives page loads and an object-cache flush.

## Troubleshooting

### I cleared the transient and nothing changed

Expected. Delete the `nxt_model_cache` option as well, then the transient again.

### Is there a way to avoid this during development?

Make definition changes through the admin where possible — that path invalidates the cache properly.

## Related Docs

- [Why is my custom field empty?](https://nexterwp.com/docs/custom-field-empty-not-showing/)- [Create a field group in WordPress](https://nexterwp.com/docs/create-a-field-group-wordpress/)

## Frequently Asked Questions

**Q: Why do field group changes on disk not show up in WordPress right away?**
A: Nexter stores field group definitions as files and also keeps a cached model, so a deploy or file copy can leave the site serving the old version. The key detail is that the cache is keyed on the index file, not the definition contents, so changes made outside the admin can be missed. That is why this looks like a cache issue instead of a broken edit.

**Q: What cache do I need to clear when field group changes are stuck?**
A: Two layers have to be cleared: the model cache option and the definitions transient. The page names them as `wp option delete nxt_model_cache` and `wp transient delete nxt_ct_definitions_v1`. Clearing only one layer can leave stale data behind, so both need to go in that order before reloading the page.

**Q: Why did clearing the transient not fix my custom field changes?**
A: The transient is only part of the chain. If `nxt_model_cache` is still present in `wp_options`, it repopulates the transient with stale data, so nothing appears to change. That is why deleting just `nxt_ct_definitions_v1` often feels like it did nothing. The fix is to remove the model cache option first, then clear the transient again.

**Q: Should I edit field group definitions in admin or on the server during development?**
A: Editing definitions through the admin is safer because that path invalidates the cache correctly. The problem described on this page only affects changes made outside the admin, such as a deploy or file copy on the server. If you are iterating quickly, admin edits avoid the stale-cache trap and save you from chasing an old rendered version.

**Q: Does object-cache flushing fix field group changes not showing?**
A: No, not by itself. The cached model lives in a `wp_options` row, so it survives page loads and even an object-cache flush. That means the stale value can keep coming back until `nxt_model_cache` is deleted directly, along with `nxt_ct_definitions_v1`. This is why a normal cache flush can look successful but still leave old field data visible.

**Q: What should I do if I cleared both caches and still see old output?**
A: A page cache or CDN can still serve old rendered output independently of Nexter’s own caches. The page says to purge that too after deleting `nxt_model_cache` and `nxt_ct_definitions_v1`. If you want a related check for missing output, [Why is my custom field empty?](https://nexterwp.com/docs/custom-field-empty-not-showing/) is the next place to look.