Marking it as a bug. I’ll take a look at it.
–David
P.S. Does this occur with the base Formidable plugin or their Pro version? Also, does this occur when Formidable is just loaded, or when they share forms on the same page?
Thread Starter
mbay
(@mbay)
Hi David,
thank you for the prompt response – much appreciated!
P.S. It is occurring with the “Pro” version installed, so I am uncertain if it will do the same with the base plug-in; if you require the pro version to test, please let me know – the “Seamless Donations” and “Formidable” forms were on separate pages.
M.
I know this is a pain, but here’s how I would test it (and since you have the Pro version, I’m going to ask if you would). I’d gen up a new, fresh WordPress install, run Twenty Thirteen as my theme, and just install Seamless Donations and Formidable Pro. I’d put the [seamless-donations] shortcode on a page and see if that results in a failure.
If that works, then it’s probably not a conflict between those two, there’s probably an additional factor.
–David
The error is from this line in seamless-donations.js
jQuery(“select[name=” + nameOfChangedSelect + “] option:selected”).each(function () {
It should be:
jQuery(“select[name='” + nameOfChangedSelect + “‘] option:selected”).each(function () {
It also a problem to have this script running when any field in any form changes. This line needs to be more specific so it only runs on Seamless donations forms.
jQuery(“form”).on(“change”, “select”, function () {
Steph, I see your first change and, without testing it, it seems on the money.
For the second, I’d made the assumption that the only form on the page was Seamless Donations. I’m not sure what the ripple effects in Seamless Donations’ reliability would be if I changed that attribute.
But… if you’re a jQuery guru (and I’m sure as heck not), I would totally welcome some detailed suggestions about how to do form-limiting without breakage.
–David
