Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with lsGetResponses #1

Open
jsibley2 opened this issue Apr 19, 2017 · 2 comments
Open

Error with lsGetResponses #1

jsibley2 opened this issue Apr 19, 2017 · 2 comments

Comments

@jsibley2
Copy link

I can get a session key and lsGetSummary works without a problem, showing 8 completed responses.
However, lsGetResponses(surveyID, completionStatus = 'complete') or just lsGetResponses(surveyID) give the following error:

Error in lsAPI(method = method, params = params, lsAPIurl = lsAPIurl) :
Server is responding but not in a proper way. Please check the API URL.

Am I missing a necessary parameter or do you have another ID of what the problem might be?

Thanks.

@kalimu
Copy link
Owner

kalimu commented Apr 20, 2017

That is strange indeed. Please check if your LimeSurvey user has access to the responses of the survey. Perhaps I could help you more, but you need to provide some code for replication (I can't replicate this issue on my surveys). You can contact me by mail as well (kamil.wais@gmail.com).

@r0bis
Copy link

r0bis commented Jul 8, 2017

Yup, I have exact same problem. I can get responses with limer but not with limeRick and I get the same kind of error message from limerick. I am sure the URL is correct. With respect to survey permissions - the user I am logging in has permissions to read responses, not anything else. The user can list surveys that he has permission to read responses from, but not get the results. Before I gave the read permission, the user could not list any surveys - response was empty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants