Hi @steigw,
I’ve looked into your form and unfortunately I’m not seeing any red flags. An “Error collecting the API response” is basically a complete failure and usually signifies some type of communication issue (like inability to run AJAX calls). I’m seeing a lot of other plugins’ JavaScript files are running on the same page – that could be the issue, but again nothing obvious.
My suggestions to debug this issue:
- Create a new form based on the same list
- Try using the non-AJAX submission method (just to see if that works
- Try disabling some of the other plugins running on the same page
I’m really sorry I couldn’t be more specific – as I said before, I’m not sure what’s happening and there’s no obvious red flags to narrow down the issue.
Kevin.
Thread Starter
steigw
(@steigw)
Turning off the AJAX submission for this plugin solved the problem, so at least people can sign up. Now for debugging. On our staging site, I’m getting a different error:
Oops! There is a problem with this form:
textStatus:parsererror
errorThrown:Error: jQuery1124007361573015982092_1487946355555 was not called
responseText:
Does this mean anything to you? I’d really like to fix it and turn AJAX back on.
Thanks
Hi @steigw,
I’m totally with you that AJAX is the better method and I will help you to get that working; non-AJAX should hopefully be a temporary work-around.
That error is indicating a JavaScript conflict – which makes sense in this case, but does not help pinpoint the cause of the conflict. I know it’s inconvenient, but in your staging environment can you try disabling other plugins one by one?
I’m looking at all of the JS files that are active on your subscribe page to see if there’s a specific plugin that is conflicting with us. So far no luck; I’ll let you know.
Kevin.
Update: I’m not seeing any obvious conflicts from other plugins’ JS files.
Let me know if you can try turning off the plugins one by one (I know it’s a pain, sorry).
Thread Starter
steigw
(@steigw)
I’m working on that aspect and will come back to you on it.
Plugin Contributor
Tracy Levesque
(@liljimmi)
🏳️🌈 YIKES, Inc. Co-Owner
Hi @steigw,
Any luck? Let us know.
Thank you!
-Tracy
Thread Starter
steigw
(@steigw)
I’ve sort of narrowed it down, but don’t have a fix yet, except keeping Yikes AJAX free. I’m still hopeful to find a final solution.
Plugin Contributor
Tracy Levesque
(@liljimmi)
🏳️🌈 YIKES, Inc. Co-Owner
Thank you for the update. I’m going to close this for now, but please feel free to comment on it at any time in the future!
Have a good day!
-Tracy