Thanks for the update and glad that it is working now.
For clarity, I'll explain both the concerns in separate points:
1. When a page loads, Toolset forms associate certain event/listener with the form input field, which is set as a source/trigger for a conditional field group.
But, if the HTML for that input field is reloaded through an AJAX request or changed through some other script, that association is broken and the conditional field group no longer responds to the changes to that triggering input field.
This is why you need the custom script from Jamal for the edit form that is loaded inside the archive loop, but not for the add new form, that is outside the archive loop.
A quick test will make this more clear:
a). From the JS editor of the "Class Archive" remove or comment out the following script line:
As a result, the "footable" script won't initialize on the table of the archive's loop.
b). From the JS editor of the "Edit Class" form, remove or comment out the script that Jamal provided.
c). Lastly, fix the generic field "class-advanced-settings" in this form, by setting the default value to "1":
( you should keep this change even after this test is completed and more on this in the next point )
[cred_generic_field type='checkbox' field='class-advanced-settings']
{
"required":0,
"default":"1",
"label":"Edit Advanced Settings?"
}
[/cred_generic_field]
Now, when you'll check the "Classes" archive page on the front-end, you'll see that the conditional field groups in both these forms will be working as expected, even without Jamal's script. That is because "footable" script won't be executing on the archive's loop.
( after the test feel free to revert the changes made in the first two steps )
2. I can understand how the use of the word "default value" for a generic checkbox field can cause some confusion. But actually, in this case, the default value corresponds with the checkbox field's "value" attribute ( ref: hidden link ) and not with its checked or unchecked state.
For this reason, when no default value is passed in the generic field's code, the checkbox input field is generated in the form, but its value attribute is empty.
I hope this explanation will make this more clear.
