Just following up — any suggestions? We are now live and would like this to work. Thanks!
I’m getting this too and came here seeking help! Thing is I already have one form set up (and working perfectly!) Now I want to set up a separate form with a different infusionsot tag and it just spinning and spinning and spinning…..
Would really appreciate any help!
First issue I’ve had with an otherwise excellent plugin, thank you!
Plugin Contributor
Zack Katz
(@katzwebdesign)
1) Please try using Chrome or Firefox if you’re not already
2) Send me the Javascript error information
3) Send me your Infusionsoft info so I can debug: support@katz.co
Uncaught SyntaxError: Unexpected identifier load-scripts.php:2
runResponse load-scripts.php:2
xmlhttp.onreadystatechange
Plugin Contributor
Zack Katz
(@katzwebdesign)
Okay, this seems to be a similar issue to another plugin, which was quickly solved once someone provided some account login credentials.
If you want this fixed, please email support@katz.co with an Infusionsoft login. FYI, I access my email using SSL (secure connection).
What is the quick solution, since I certainly am not sending my login credentials via email?
Thanks
Hi Zack – I need to get permission from the client to share their API info with you, I can do that but is there perhaps something you might have us try first?
I’m also hesitant to send it the data via email, even if you access it via SSL. If needed, I’ll email you a temporary admin login to the WP site.
Plugin Contributor
Zack Katz
(@katzwebdesign)
This is fixed now, thanks to @sonora33. It was a problem with tags having non-alphanumeric characters that broke the script.
Please review the plugin on WordPress.org!
Thank you Zack – I’ve installed the update to the plugin and it’s working now. Much appreciated!
These forums work best if there is an answer posted. I see that sonora33 helped somehow, but I don’t see where this was answered. I could really use some info right now!
You are right @mcgeorge40 — I hate unanswered q’s when I’m looking for a solution.
if I remember correctly, Zack went in with my login to troubleshoot, and then released an update to the plugin to resolve he issue. I don’t know exactly what he did.
Best of luck!
