Michal Kleiner

Yep, that'd be a bug. The PHP values should only be used as fallbacks if there's no other config provided.

If the dark mode was the last thing remaining to do in the CMS UI, then why not. At the moment I'd say there are bigger problems to solve first.

Hi @kevingroeger, CMS 5 will be released in the coming weeks and is in feature freeze at the moment. This has missed the cut off, CMS 5 didn't really need...

Moved the issue to the admin module. @Blueace if you want to open an enhancement PR against the `2` branch we can certainly review it.

Hello! Thank you for raising the issue and apologies it hasn't been responded to earlier. The issue is a bit outdated and we're now on Silverstripe CMS 4.12.0 and Display...

My guess is there's some custom JS within the CMS itself using this particular field which then interferes with Display Logic.

I'd be happy to look at a PR that adds support for array-style field names (`FieldName[]`), if we could also add some tests for that.

Hello @digitall-it! Thank you for raising the issue and apologies it hasn't been responded to earlier. Since the issue is outdated and we're now on Silverstripe CMS 4.12.0 and Display...

Would this mostly happen with front-end forms? How would you get a field with the same name in two forms on one page in the CMS?

I guess you're using `hideUnless` controlled by the 'with house' and it's hidden by default. I would say that would be a limitation of the mechanism as it's currently implemented....