Disabled fields cannot be updated programmatically

The CMS Questions
1

I am experiencing the exact same as described here, but in v5.0.3: https://forum.getkirby.com/t/k4-programatically-update-disabled-field/30533
Didn’t have that issue in 4.7.0 (even without impersonating kirby). Is this a regression or am I missing something else.

For context: I am collecting data from an API. That is triggered with a button in the panel (i.e. I am logged in as an admin). Fields, that are set to disabled: true in the blueprint are “updated” to an empty value. Removing the disabled setting, they are receiving the assigned value, as any other field.

2

I cannot directly reproduce this - it seems to work for me. If you have a small reproducible setup (e.g. with plainkit) that would be great.

3

Retried with a plainkit and found, that a “regular”, disabled field of type: text I can update programmatically, but not a text field inside a structure field.
This used to work before.

Here’s a ZIP file of the plainkit (with the updating taking place in site/templates/default.php and the fields being part of site/blueprints/default.yml): SwissTransfer - Send large files securely and free of charge

4

Kirby v5.0.4 fixed this issue. Thanks!

1 Like