Support

Account

Forum Replies Created

  • Hi —

    I have found that setting readonly to 1 works for text fields, but not for fields of other types — if there’s a widget, the widget still functions (*and* changed values are saved). In my case I have both a select of users and a radio dialog box.

    Currently I am getting around this by converting each field to a text field in the load_field filter, plus setting it to readonly.

    But this feels very hacky and fragile — I already ran into a problem where I had switched between saving the label or the value of a choice and it broke.

    So I would like to add my vote for official support of the ability to dynamically set a field to readonly, and have that work for widgets as well.

  • I would like to add a big +1 to this as a basic feature request. I have a scenario in which fields may or may not be changeable based on other state. Affected fields include a select field, a radio field and a text field. Having to code up separate workarounds for each case is a pretty high cost to pay for some pretty straight-forward functionality.

Viewing 2 posts - 1 through 2 (of 2 total)