|
|
After this error, whenever I try to save the question, same blank error appears |
|
|
|
Also reproductible on 3.22.8_200309.
Dropped database and recreated but the issue is still reproductible.
Docker image "martialblog/limesurvey:3.22.8_200309-fpm-alpine" and postgres docker image "postgres:11.5-alpine" |
|
|
|
After this error, editing question and saving the question results in same error and the view shows the updated changes, but actually the changes are discarded.
If I click "Preview Survey", the question is in the initial state before the error. |
|
|
|
Uploaded a video with this issue: https://vimeo.com/399196405 |
|
|
|
Note that because of this error I'm unable to use LimeSurvey. |
|
|
|
Postgres? Then it's probably fixed, please wait for the coming release and try again. |
|
|
|
Yes, i'm using postgres 11.5 |
|
|
|
Please update to the latest version and try again. Thank you. |
|
|
|
Issue still occurs using 4.1.12_200324 |
|
|
|
This issue should have highest priority as it doesn't allow me to create a survey, thus I cannot use this software.
I cannot update issue to change priority. |
|
|
|
Still using LS from docker? |
|
|
|
Yes, image: martialblog/limesurvey:4.1.12_200324-fpm-alpine |
|
|
|
Since you're the only one with this problem, I'd either
1) Ask martialblog about the problem, or
2) Run without docker |
|
|
|
Also try the forum for more help. |
|
|
|
Docker is a must for production use.
Limesurvey seems a nice project but I cannot use it.
Instead, I've resolved to using SurveyJs frontend and some backend code for my use case. |
|
|
|
There are multiple ways one can use docker. For example, you can put the source code on the server and PHP inside docker.
Glad you found a solution. ;) |
|
|
|
Won't fix docker problems. |
|
|
|
Another Mantis problem... Other user that replicated this issue cannot add a note or reopen this one.
He now must open a duplicate issue that will reference this one, adding complexity and separating bug tracking details.
https://github.com/martialblog/docker-limesurvey/issues/28 |
|
|
|
I recently fixed the "blank error". The error will now contain an error message, but it doesn't fix the underlying issue. |
|
|
|
@cdorin Can you have a look at this, see if you can reproduce? I think I encountered it during quota testing (not related to quota, but still). |
|
|
|
Hi,
just wanted to add my findings here as well. Hope it helps:
- This only happends with Postgres. I tested a MySQL installation and everything works as expected, no error.
- The Popup Error is attached
- The error in the application log is this:
2020/03/28 04:13:01 [warning] [application] Failed to set unsafe attribute "aid" of "Answer".
2020/03/28 04:13:01 [warning] [application] Failed to set unsafe attribute "en" of "Answer".
2020/03/28 04:13:01 [error] [exception.LSJsonException.500] LSJsonException: Question has been stored, but an error happened:
in /var/www/html/application/controllers/admin/questionedit.php:297
Stack trace:
#0 [internal function]: questionedit->saveQuestionData(762155)
#1 /var/www/html/framework/web/actions/CAction.php(109): ReflectionMethod->invokeArgs(Object(questionedit), Array)
#2 /var/www/html/application/core/Survey_Common_Action.php(86): CAction->runWithParamsInternal(Object(questionedit), Object(ReflectionMethod), Array)
#3 /var/www/html/framework/web/CController.php(308): Survey_Common_Action->runWithParams(Array)
#4 /var/www/html/framework/web/CController.php(286): CController->runAction(Object(questionedit))
#5 /var/www/html/framework/web/CController.php(265): CController->runActionWithFilters(Object(questionedit), Array)
#6 /var/www/html/application/controllers/AdminController.php(172): CController->run('questioneditor')
#7 /var/www/html/framework/web/CWebApplication.php(282): AdminController->run('questioneditor')
#8 /var/www/html/framework/web/CWebApplication.php(141): CWebApplication->runController('admin/questione...')
#9 /var/www/html/framework/base/CApplication.php(185): CWebApplication->processRequest()
#10 /var/www/html/index.php(182): CApplication->run()
#11 {main}
REQUEST_URI=/index.php/admin/questioneditor/sa/saveQuestionData/gid/1/sid/762155
HTTP_REFERER=http://localhost:8888/index.php/admin/questioneditor/sa/view/surveyid/762155/gid/1/qid/1
2020/03/28 04:13:02 [warning] [application] Failed to set unsafe attribute "code" of "QuestionType".
2020/03/28 04:13:02 [warning] [application] Failed to set unsafe attribute "description" of "QuestionType".
2020/03/28 04:13:02 [warning] [application] Failed to set unsafe attribute "group" of "QuestionType".
2020/03/28 04:13:02 [warning] [application] Failed to set unsafe attribute "subquestions" of "QuestionType".
2020/03/28 04:13:02 [warning] [application] Failed to set unsafe attribute "hasdefaultvalues" of "QuestionType".
2020/03/28 04:13:02 [warning] [application] Failed to set unsafe attribute "assessable" of "QuestionType".
2020/03/28 04:13:02 [warning] [application] Failed to set unsafe attribute "answerscales" of "QuestionType".
2020/03/28 04:13:02 [warning] [application] Failed to set unsafe attribute "class" of "QuestionType".
My Setup:
root@server:~# apache2 -V
Server version: Apache/2.4.38 (Debian)
root@server:~# psql --version
psql (PostgreSQL) 11.7 (Debian 11.7-0+deb10u1)
root@server:~# php --version
PHP 7.3.14-1~deb10u1 (cli) (built: Feb 16 2020 15:07:23) ( NTS ) |
|
|
|
Thank you! I've applied a fix that creates a proper error message, but it's not tested and merged yet. We'll have to wait for next Monday release, then test again. (Or you can apply the fix manually if you like.) |
|
|
|
Please check if this bug still exists in the latest patch release. Thank you. |
|
|
|
Hi,
yeah looks good now. I tested both 3.25.15+210223 and 4.4.10+210222 with Postgres and there is no error.
good job! Can be closed.
Cheers, Markus |
|
