Resolved
Reported for: Toolset Forms 1.9
Resolved in: Toolset CRED 1.9.1
CRED forms can contain custom JavaScript code provided by users to extend their functionality, or to add external libraries to enhance those forms.
In CRED 1.9, we changed the way we initialize CRED forms. In some browsers, that custom JavaScript code might not be properly managed, which might prevent it from running when it is supposed to.
This issue will be fixed in the next version of Toolset CRED. In the meantime, this patch can be applied by unzipping it and uploading the file it contains to replace the one with the same name, located in the ../public/js/ folder.
Please note that this patch was created against CRED 1.9.0.1, but it can also be used against CRED 1.9.
I am so glad that I looked in the errata and that someone actually discovered this. I recently upgraded to most recent versions of Types and Cred and this broke my custom JS modal alert.
Please Toolset Devs, be mindful of the constant changes. This is my single most frustration as user reliant on third party plugins, especially one with as much depth as Toolset.
Being only a minor upgrade back, I expressed my hesitation to upgrade to a support memeber as things are continually changing in toolset plugins that render sites or site features disabled to the site owners that depend on them. Much to my dismay, this was once again the case.
For me, no console error was being displayed so that really left a number of possibilities that would cost many hours of troubleshooting. Whether or not a css change was affecting it, or a naming convention of ID suffixes (which was another recent CRED change), or whether or not my js and css files were still being enqueued properly.
Luckily for me, this solved the issue.