Closed (won't fix)
Project:
SurveyGizmo
Version:
6.x-1.0-beta1
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
24 Jun 2010 at 19:39 UTC
Updated:
27 Jan 2015 at 22:57 UTC
Jump to comment: Most recent
Comments
Comment #1
garbanzito commentedMark, I'll need more info to help with this. The stand-alone page will be easier to debug -- Are you sure you have access permission to the path? Does the page load at all, or give a 404? Is there a JavaScript call to SurveyGizmo in the page source (a script tag with src="http://www.sgizmo.com ...")?
Also try creating a new survey at SurveyGizmo, then setting it up via this module. If this survey loads, but your others don't, I think this is a feature of SurveyGizmo.com which I've seen but I don't think this module can control -- something i plan to explore with SurveyGizmo.
Comment #2
nmcclain commentedMark,
I just had the same problem. I looked at the $survey object that is returned by surveygizmo_get_survey_obj(), and the "js_embedingcode" field was empty! After logging into SurveyGizmo and clicking "view embed code" for my survey, it just started working. I think that SurveyGizmo must not generate the JS embed code until you have looked at it in their GUI. I don't think this needs to be fixed in this module, although maybe it'd be nice to add some error handling if the embed code comes back empty...
Hope this helps!
Garbanzito,
Thank you for an awesome module!!!
Ned.
Comment #3
garbanzito commentedThanks for the diagnosis, Ned. If that's indeed what's happening, we should address it. I'll see if I can reproduce your scenario, since when I've seen surveys not load, js_embeddingcode has contained a valid script call, but surveygizmo.com hasn't generated a survey. I'm also pretty sure I've embedded surveys where I've never viewed the embed code at surveygizmo.com, so there may be a more subtle trigger ...
Anyhow, the error handling I foresee would be to react similarly to how we do to timeouts from surveygizmo.com:
And/or to log it.
Comment #4
safetypinI'm closing all 6.x issues, as the old API was deprecated, and all issues are currently irrelevant. If you're interested in a 6.x version of the module that uses the new API, please use a different issue for that request.