Fieldset not working as expected?

[stephenmeehanuk]

Hi

• I've created a duplicate hero fieldset
• Made some changes
• It uses the same handles, so the fields are populated with data from the .md file
• When I remove the original fieldset, the new fieldset doesn't display properly?
• It's missing fields?

Bit tricky to explain, so I've made a short video showing the issue.

blueprint-2.mp4

Environment
Application Name: 
Laravel Version: 11.44.2
PHP Version: 8.3.19
Composer Version: 2.8.6
Environment: local
Debug Mode: OFF
URL: lbf-com.test
Maintenance Mode: OFF
Timezone: America/New_York
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: redis
Database: sqlite
Logs: stack / single
Mail: log
Queue: redis
Session: file

Livewire
Livewire: v3.6.2

Statamic
Addons: 6
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.52.0 PRO

Statamic Addons
jonassiewertsen/statamic-jobs: 1.5.0
jonassiewertsen/statamic-live-search: 2.2.0
marcorieser/statamic-livewire: 3.9.0
statamic/collaboration: 1.0.0
statamic/importer: 1.8.1
visuellverstehen/statamic-anchor-navigation: 1.0.0

[edalzell]

If you can reproduce this on a new, clean Statamic site, please open an issue

[duncanmcclean]

What does the new fieldset look like? Can you provide the contents of the YAML file?

I'm just wondering if you might have conditional fields setup pointing at one of the fields you've removed from the new fieldset.

[stephenmeehanuk]

Ah! Good suggestion, that was the 'problem'. I removed the button group in the duplicated fieldset that was originally being used to control the conditional fields.

Thanks for the nudge Duncan :)