View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
13496Bug reportsSurvey participants (Tokens)public2018-03-19 00:212018-03-21 10:40
Reporteracury Assigned To 
PrioritynoneSeveritycrash 
Status closedResolutionno change required 
Product Version3.3.x 
Summary13496: Preview Error
Description

when I try to check the preview of the questions in admin (even logged in as admin), I get the message:
"This survey is currently not active. You will not be able to save your responses."

Error Occurs in Version 3.5.3 + 180316

Steps To Reproduce

Edit questionnaire.
Click View Questionnaire

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build) Version 3.5.3 + 180316
I will donate to the project if issue is resolvedYes
BrowserAll
Database type & versionMysql 5.6.35
Server OS (if known)Linux
Webserver software & version (if known)Windows Server 2016 - IIS/10.0
PHP Version7.1.13

Users monitoring this issue

acury

Activities

ollehar

ollehar

2018-03-19 10:26

administrator   ~47108

This is not a bug. This message is always shown when the survey is not active.
acury

acury

2018-03-19 12:54

reporter   ~47123

Hello, how are you ?
But until version 2.x I was able to test the survey before activating it, during the edition as admin logged in we clicked on this button and it was possible to visualize how it was getting.
Do not have this option in version 3.x anymore? Why is it necessary to activate the questionnaire just to test a question or group, then it will be necessary to unpack the questionnaire to re-edit it ... :-(

Thank you
ollehar

ollehar

2018-03-19 13:49

administrator   ~47125

Oh, you mean you see ONLY this message? If so, yes, that's a bug. Sorry for the misunderstanding. Could you please attach a survey which reproduces the issue? And also a screenshot of the button/link you click. Thank you.
acury

acury

2018-03-20 19:37

reporter   ~47147

Hello good afternoon,
The problem was solved by booting the machine, and switching to another Mysql database.
Thanks for the feedback, in case similar problems occur again I warn them

Issue History

Date Modified Username Field Change
2018-03-19 00:21 acury New Issue
2018-03-19 10:26 ollehar Note Added: 47108
2018-03-19 10:27 ollehar Status new => closed
2018-03-19 10:27 ollehar Resolution open => no change required
2018-03-19 12:54 acury Status closed => feedback
2018-03-19 12:54 acury Resolution no change required => reopened
2018-03-19 12:54 acury Note Added: 47123
2018-03-19 12:54 acury Issue Monitored: acury
2018-03-19 13:49 ollehar Note Added: 47125
2018-03-20 19:37 acury Note Added: 47147
2018-03-20 19:37 acury Status feedback => new
2018-03-21 10:40 ollehar Status new => resolved
2018-03-21 10:40 ollehar Resolution reopened => no change required
2018-03-21 10:40 ollehar Status resolved => closed