Tokens not supported in field name in action with template 'form field: get submitted value'

AFAIK this was a deliberate decision to not support tokens here, as the field name may already contain [ and ] characters for nested form fields. If nothing else, we need to remove the description that tells the user otherwise.

@mxh can we support tokens in that field safely? Looks like we do support tokens in form field names in other actions, e.g. "Set default value", but not here.

can we support tokens in that field safely?

Probably yes, created MR384 that adds token replacements. Please have a look.

Just seen that the OP also asked for how to set default values on a checkboxes field. Attached an example model for that.

Unfortunately, I encountered a bug while trying to set default values on a checkboxes fied. A fix for that is available in the linked issue. You'd need to apply the fix in that issue first, otherwise the attached example won't work.

Very nice that this also covers related plugins with similar context, thanks a lot.

I tend to back port this to 1.1.x as well, since the field description stated that tokens were supported, while they didn't. So, this could be seen as a bug by users.

Merged and back ported to 1.1.x

Ah, just seen that I accidentally posted #7 in the wrong issue, reverting. It was meant for 💬 How to disable single checkbox and set default values in multi-value checkboxes form elemen Fixed , where I copy-pasted the comment now.

Automatically closed - issue fixed for 2 weeks with no activity.