Using the suggested code [surveygizmo:"surveyid"] doesn't work, also trying to see the survey from the administration/setting page doesn't work, managing however works fine (goes rightaway to "my" GizmoSurvey site). At the moment I am using an Iframe code on my pages, and that does work! So connection, license, type of survey etc. isn't a problem...

Comments

garbanzito’s picture

Assigned: Unassigned » garbanzito
Status: Active » Postponed (maintainer needs more info)

Can you please say what happens when it "doesn't work" ... Does the SurveyGizmo token display instead of the survey? Does the token disappear from the content but the survey doesn't appear? In the rendered page, is there a JavaScript call to SurveyGizmo in the page source (a script tag with src="http://www.sgizmo.com ...")?

Also please confirm that you have have added the SurveyGizmo input filter to a new or existing input format, and that that input format is enabled for the content in which the survey token is embedded.

BasH’s picture

When clicking Show page in my SurveyGizmo Dashboard (admin/content) I only see the survey title. When I choose Manage, I can set "active", "stand alone" and a path. When I submit this page I also only see the survey title.

There is no javascript call in the page source.

I have added the Survey Gizmo input filter and enabled this input format for this content.

Trying to use a token in plain text, my page content is:
Text example [surveygizmo:370720] with a survey in between.
and this is what appears on my page:
Text example
with a survey in between.

So it just doesn't show the survey.

However, using a page with PHP format and an iframe something like below, does work OK.

<iframe src="https://www.surveygizmo.com/s3/370720/SurveyTitle?uid=<?php echo $drupaluser ?>" frameborder="0" width="650" height="850" ></iframe>
garbanzito’s picture

There is no "Show page" link on the dashboard, do you mean the "view" link on the dashboard at the right end of the row listing your survey?

if you see the "view" link, you have set a path at which the survey will render standalone (not embedded in other content), if you click that link and the survey does not render then something (either on your site or at SurveyGizmo's end) is interfering with the JavaScript call. One possibility is that you are running something like NoScript in Firefox (I say "like" because NoScript itself will leave the script call in the source howe).

Try turning off JavaScript in your browser and reloading the page (either embedded or standalone) -- do you now see in the page source a script tag with "src="http://www.sgizmo.com ..."? If so, the module is doing its work to insert the call to SurveyGizmo, but SurveyGizmo's script is not running correctly.

If there are other JavaScript widgets on the page where the survey should render, try a test rendering on a page without such widgets. This module can't control the script that SurveyGizmo supplies. I have seen some interactions where SurveyGizmo's script interfered with other scripts, but not the other way around. If we can pinpoint interaction problems, there might be a workaround or some feedback to SurveyGizmo that would be helpful

BasH’s picture

I'm using a translated module, thought it was Show Page, but View it will be (indeed at the right end of the survey).

I will check it later, (have to do this on another location). By the way, can firewalls or something like this also interfere with the scripts?
I also have to check if I can turn off the scripts in the environment I am testing this site..().

I will edit this comment later, thanks for your reply, Bas H.

hanno’s picture

Same issue here, survey content not shown on the path.

garbanzito’s picture

Hanno, there is not enough info to know whether this is a problem with the module. Please try the suggestions in paragraphs 2 & 3 of comment #3 and report back with the results.

hanno’s picture

Embedding without this module with iframe works. Note that with embedding with javascript I had an issue with conflicting javascript of Drupal and SurveyGizmo.

I used the solution found at http://www.5limes.com.au/blog/?p=26

    Immediately before the SG injection script add the following:

    <script> var JQ$ = $; </script>

    Add SG injection script as normal

    Immediately after the SG injection script add the following:

    <script> $ = JQ$; </script>
hanno’s picture

Status: Postponed (maintainer needs more info) » Active

OK, did some research, and if I print something else at the page of that path it works fine for example: ((string)$survey->id)

The issue is that $survey->js_embedingcode is empty

It seems that SurveyGizmo is not delivering javascript anymore in their API, see:
http://developer.surveygizmo.com/forum/topic/how-to-obtian-javascript-em...

That would mean this module is broken as long as this isn't fixed by SurveyGizmo?

garbanzito’s picture

Thanks for the further info. There are two issues here:

Comment #7 may help resolve the problem of conflicting JavaScript on the page. The discussion you reference makes sense and I will pursue its suggestion. I will break this out into a separate issue.

Comment #8 is what I see as the focus of this issue: SurveyGizmo failing to provide the JS embed in response to the call. I have only rarely seen this — when I have it has appeared to be a transient problem, so I had assumed it was a problem at the SurveyGizmo end, or possibly throttling in response to overuse of the API when I was testing.

The discussion you refer to implies the "legacy API" is still working, which is what this module uses. I will do some tests and contact SurveyGizmo if the API appears to have stopped working. Otherwise I will need to isolate why some calls get a response and some do not.

hanno’s picture

Ok, can it be that it relates to the SurveyGizmo account? Maybe newer accounts doesn't work with the older API functionality anymore?

safetypin’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

I'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.