Orderable property won't save in collection

[DennisMeene]

Bug description

When activating "orderable" in a collection and saving, the changed property won't be saved.

How to reproduce

See bug description.

The bug occurs in versions newer than 5.67.0. On 5.67.0 it works as intended.

Logs

Environment

Environment
Application Name: XXX
Laravel Version: 12.37.0
PHP Version: 8.4.14
Composer Version: 2.8.12
Environment: local
Debug Mode: ENABLED
URL: cgate.test
Maintenance Mode: OFF
Timezone: UTC
Locale: de

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

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

Storage
public/storage: NOT LINKED

Statamic
Addons: 2
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.69.0 PRO

Statamic Addons
hph/base: dev-main
kabocom/soft-hyphens: 1.0.0

Installation

Starter Kit using via CLI

Additional details

No response

[miicah]

As a workaround you can get it to save if you toggle on expect a root page, slugs or max depth.

I'm not sure why it's not saving the YAML if they are all null/false.

[lukeagsmith]

I have this too in Statamic 5.70.0, but @miicah that workaround doesn't work for me.

None of the structure settings save in the yaml even if change settings that are added to the yaml manually.

[wesort]

Same here.

Workaround

For me, saving the following the collection's .yaml has worked:

structure:
  root: false
  max_depth: 1

[jasonvarga]

Note to self: Caused by #11150