Forums

For a field (example: checkbox), under Events, you can only put in one element identifier and not a comma separated list (which would be great). You can get around this a little bit by adding a class to each element you want to be affected at once - but still.

The Enable and Show actions don't work to enable/show or hide/disable a checkbox when selected using a class, or using the id, but they do correctly enable/disable validation. To have them show/hide and enable/disable the checkbox you have to target the checkbox name. EDIT: adding a class to a checkbox under advanced -> container class doesn't actually add the class.

When targeting the class of a text field, the show/hide and enable/disable actions work, but the enable validation / disable validation action does not.

The disable action will disable the input of a checkbox, but will only add a "disabled" class to the containing div of text fields (and I assume other field types) - EDIT: it will disable the field itself when targeting the field name, not when targeting the class

If you uncheck "Enable ghost" on a checkbox, and target it with the checkbox name in a hide+disable+disable validation action, it will disable and disable validation but it will not hide it.

If you uncheck "Enable ghost" on a checkbox, and target it with a class in a hide+disable+disable validation action, it will not disable or hide the checkbox, and if the checkbox is required and moves (for example because other fields above it are hidden) then the red required asterisk will stay in the same place on the page and not move with the checkbox.

Alright this is getting too confusing and too complicated. I made a form demonstrating exactly what I'm talking about.

Also the event "disable validation" doesn't disable validation for the "Validate Fields" server action.

Hi healyhatman,

Some of your selectors are not correct, you can not target the elements by the classes of their containers, you can howvere do the following:

.container_class :input

and that would select the inputs inside that container, which is element itself.

Please try to fix this in the test form and let me know what you find.

You should also upgrade to v6.0.7 first.

Best regards,
Max

Yep but did you see the problems with the group that were targeted correctly by field name?

I tried that and it does nothing😟

Hi healyhatman,

Could you please attach a new test form so I can check it here ?

Best regards,
Max

Sure tomorrow. Can you make it so cf6bak files here?

Hi healyhatman,

The forum is currently configured to accept Chronoforms v6 backup files as attachments, let me know if this does not work!

Best regards,
Max