[Appearance & Branding] configuration in read only mode can be modified

[heigpa]

Steps to reproduce

• Make sure the configuration for 'Apperance & Branding' is read only
• Login as admin
• Change some config options (e.g. some color)

Actual behaviour

• Options can be changed allthough config is read only
• Configuration can not be saved

Expected behaviour

• If the configuration is read only. it should not be possible to change any of the options in the configuration

Environment

• Studio Nightly
• Windows

[markus-moser]

In the /pimcore-studio/api/settings/admin endpoint the writeable flag is false although it's configured as settings-store write_target

[mcop1]

@markus-moser At least when I look here https://github.com/pimcore/demo-enterprise/blob/2025.x/config/config.yaml#L283-L294, I dont see it configured to use settings-store, the key is missing, it should default to symfony-config then. Fyi, we separated the config from the old classic ui config.

@heigpa Additionally, I think your problem is more ui related, right? Problem isnt, that the save is read only, but if the save button is read only, then the whole page should be read only too, right?

@both Should I add the admin_settings configuration to demo enterprise? And make it use settings-store?

[heigpa]

@mcop1 yes, the problem described in this issue is that the configuration can be changed even in read only mode.
The problem with not being able to save is described here: pimcore/studio-backend-bundle#1653

[markus-moser]

@mcop1 on studionightliy it's definitly already on settings-store, but this doesn't help, the writeable flag of the mentioned endpoint is still false. The UI reacts correctly to the flag.

JFYI, I changed it here for nightly: https://github.com/pimcore/demo-dev/commit/0618babb9283f0a17405bcc21e2d1bf85aed3aaa

Integrating it directly in the demo would be a good idea

[markus-moser]

but yes, the readonly form in addition to the disabled save button would be a separate UI topic

[markus-moser]

My descriptions are more like for this issue:
pimcore/studio-backend-bundle#1653

sorry for that

[mcop1]

Aaaaah ok, got it, and thanks for mentioning the changing in demo-dev, I will have a second look.