LimeSurvey bugs and feature requests - Issues

20568: Implicit conversion from float 0.5 to int loses precision

Thu, 18 Jun 2026 17:43:02 +0200

With crypted attribute , when try to get quartile, we cast as float, not if not crypted.

1. No reason of cast if we do not cast when not crypted (must cast as both)
2. Throw an error with debug set

20566: Invalid tip for allowed host

Tue, 16 Jun 2026 10:36:34 +0200

To set allowedHosts, you can use config.php or generated file application/config/allowed_hosts.php
But the tip show only allowed_hosts.php even if it was not used

20564: Sporadic missing language details

Mon, 15 Jun 2026 10:19:53 +0200

Since a year and across several updates, for a few surveys (in the magintude 1 out of 100), the following error occurs sometimes for some users when they list their surveys in the admin panel:

*500: Internal server error - Survey language settings (de) not found. Please run the integrity check from the main menu.*

As suggested, running the integrity check from main menu is not viable because our tables are much too huge, which leads to a request timeout.

When the sysadmin searches for the affected user in the web UI to list the user's surveys, also the admin will be presented the same error message.

The fix is definitely the following.

First, determine if this is really the problem:

```SQL
SELECT COUNT(*) AS broken_surveys
FROM lime_surveys s
LEFT JOIN lime_surveys_languagesettings sl
ON s.sid = sl.surveyls_survey_id
AND s.language = sl.surveyls_language
WHERE sl.surveyls_survey_id IS NULL;
```

If this does not show "0", then the mentioned problem occurs. This happend several times for us.

Determine if the reporting user is affected:

```SQL
SELECT s.sid, s.owner_id, u.users_name, u.full_name, s.language
FROM lime_surveys s
JOIN lime_users u on s.owner_id = u.uid
WHERE s.sid IN (
SELECT s.sid
FROM lime_surveys s
LEFT JOIN lime_surveys_languagesettings sl
ON s.sid = sl.surveyls_survey_id
AND s.language = sl.surveyls_language
WHERE sl.surveyls_survey_id IS NULL
)
ORDER BY owner_id;
```

Fix the problem for all users in one go:

```SQL
INSERT INTO lime_surveys_languagesettings
(
surveyls_survey_id,
surveyls_language,
surveyls_title
)
SELECT
sid,
language,
CONCAT('Recovered survey ', sid)
FROM lime_surveys s
WHERE NOT EXISTS (
SELECT 1
FROM lime_surveys_languagesettings sl
WHERE sl.surveyls_survey_id = s.sid
AND sl.surveyls_language = s.language
);
```

Re-check with the following steps above (web UI and the two SELECT-queries), the issue should be gone.

20563: Translation file with incorrect information

Mon, 15 Jun 2026 13:19:54 +0200

We are facing the problem that languages for text elements get messed up when exporting a multi-language survey in the tab-separated format.

We have a survey with three languages. For several questions, we filled the fields for validation tips, answer prefixes and other replacement texts in all three languages. However, when we export the survey in the tab-separated format, the respective fields are not filled with the correct language anymore. Instead, in the base language, they are filled with what seems to be the language that was last modified in that question. In the lines for additional languages, they remain completely empty. We are thus not able to make any bulk modifications or even have the entered translations checked outside of LimeSurvey as we cannot export the survey in the tab format without a) losing the translations we entered and b) overwriting the base language with text from the wrong language upon reuploading the document.

The problem first occurred on our LimeSurvey installation with a large trilingual survey (German-Ukrainian-Russian) but was recreated for demonstration on a personal free account with a simple two-question survey in German (base language), English and French.

20562: {TOKEN_COUNTER} not documented for dummies particpant

Fri, 12 Jun 2026 18:11:27 +0200

When you create dummies participant, you can add {TOKEN_COUNTER} to have different participant, but no information

20557: calling `get_question_properties` without optional parameters crashes

Wed, 10 Jun 2026 10:58:52 +0200

The PHP call `$ls->get_question_properties($key,$code)` results in

```
PHP Fatal error: Uncaught Exception: Request error: Eigenschaft "DefaultValue.defaultvalue ist nicht definiert. in [...]/limesurvey/application/libraries/jsonRPCClient.php:162
Stack trace:
#0 [...]: jsonRPCClient->__call()
#1 [...]
#2 {main}
thrown in [...]/limesurvey/application/libraries/jsonRPCClient.php on line 162
```

IMHO this can be fixed by replacing in `application/helpers/remotecontrol/remotecontrol_handle.php`, function `get_question_properties` the following part (located at the very end of the function):

```
$aResult['defaultvalue'] = DefaultValue::model()->with('defaultvaluel10ns')
->find(
'qid = :qid AND defaultvaluel10ns.language = :language',
array(':qid' => $iQuestionID, ':language' => $sLanguage)
)
->defaultvalue;
```
by
```
$aResult['defaultvalue'] = DefaultValue::model()->with('defaultvaluel10ns')
->find(
'qid = :qid AND defaultvaluel10ns.language = :language',
array(':qid' => $iQuestionID, ':language' => $sLanguage)
)
->defaultvaluel10ns[$sLanguage]->defaultvalue;
```

20556: Can not filter statistics by Single Choice nor Multiple Choice

Tue, 09 Jun 2026 18:48:55 +0200

I started survey with one Single Choice and Multiple Choice question. In version 6.17.7 it filters correctly. In Version 7.0.0 it doesn't.

For Single Choice it doesn't do any filtering, showing the full results.

But for Multiple Choice it rises a Server Error 500 or with debugging on a "PHP warning":

"Array to string conversion"

/var/www/html/limesurvey/application/helpers/admin/statistics_helper.php(452)

440 $selects[] = Yii::app()->db->quoteColumnName(substr($pv, 0, -1)) . " > " . sanitize_int($_POST[$pv]);
441 }
442 if (substr($pv, strlen($pv) - 1, 1) == "L" && $_POST[$pv] != "") {
443 $selects[] = Yii::app()->db->quoteColumnName(substr($pv, 0, -1)) . " < " . sanitize_int($_POST[$pv]);
444 }
445 }
446
447 //T - Long free text
448 //Q - Multiple short text
449 elseif (($firstletter == "T" || $firstletter == "Q") && $_POST[$pv] != "") {
450 $selectSubs = array();
451 //We interpret and * and % as wildcard matches, and use ' OR ' and , as the separators
452 $pvParts = explode(",", str_replace('*', '%', str_replace(' OR ', ',', (string) $_POST[$pv])));
453 if (is_array($pvParts) and count($pvParts)) {
454 foreach ($pvParts as $pvPart) {
455 $columnName = substr($pv, 1, strlen($pv));
456 $encryptedValue = getEncryptedCondition($responseModel, $columnName, $pvPart);
457 $selectSubs[] = Yii::app()->db->quoteColumnName($columnName) . " LIKE " . App()->db->quoteValue($encryptedValue);
458 }
459 if (count($selectSubs)) {
460 $selects[] = ' (' . implode(' OR ', $selectSubs) . ') ';
461 }
462 }
463 }
464

Stack Trace
#0
–
/var/www/html/limesurvey/application/helpers/admin/statistics_helper.php(3635): buildSelects(array("datestampE", "datestampG", "datestampL", "idG", ...), 832198, "de-informal")

3630
3631
3632 /**
3633 * Start generating
3634 */
3635 $selects = buildSelects($allfields, $surveyid, $language);
3636
3637 //count number of answers
3638 $query = "SELECT count(*) FROM {{responses_$surveyid}}";
3639
3640 //if incompleted answers should be filtert submitdate has to be not null

#1
–
/var/www/html/limesurvey/application/controllers/admin/Statistics.php(472): statistics_helper->generate_html_chartjs_statistics(832198, array("datestampE", "datestampG", "datestampL", "idG", ...), array("datestampE", "datestampG", "datestampL", "idG", ...), 0, ...)

467 //Show Summary results
468 if (isset($summary) && $summary) {
469 $outputType = Yii::app()->request->getPost('outputtype', 'html');
470 switch ($outputType) {
471 case 'html':
472 $statisticsoutput .= $helper->generate_html_chartjs_statistics($surveyid, $summary, $summary, $usegraph, $outputType, 'DD', $statlang);
473 break;
474 case 'pdf':
475 $helper->generate_statistics($surveyid, $summary, $summary, $usegraph, $outputType, 'D', $statlang);
476 exit;
477 break;

#2
unknown(0): Statistics->run(832198, null)
#3
+
/var/www/html/limesurvey/vendor/yiisoft/yii/framework/web/actions/CAction.php(114): ReflectionMethod->invokeArgs(Statistics, array(832198, null))
#4
–
/var/www/html/limesurvey/application/core/SurveyCommonAction.php(86): CAction->runWithParamsInternal(Statistics, ReflectionMethod, array("surveyid" => 832198, "sa" => "index", "iSurveyId" => 832198, "iSurveyID" => 832198, ...))

81 $oMethod = new ReflectionMethod($this, $sDefault);
82 }
83
84 // We're all good to go, let's execute it
85 // runWithParamsInternal would automatically get the parameters of the method and populate them as required with the params
86 return parent::runWithParamsInternal($this, $oMethod, $params);
87 }
88
89 /**
90 * Some functions have different parameters, which are just an alias of the
91 * usual parameters we're getting in the url. This function just populates

#5
+
/var/www/html/limesurvey/vendor/yiisoft/yii/framework/web/CController.php(308): SurveyCommonAction->runWithParams(array("surveyid" => 832198, "sa" => "index", "iSurveyId" => 832198, "iSurveyID" => 832198, ...))
#6
+
/var/www/html/limesurvey/vendor/yiisoft/yii/framework/web/CController.php(286): CController->runAction(Statistics)
#7
+
/var/www/html/limesurvey/vendor/yiisoft/yii/framework/web/CController.php(265): CController->runActionWithFilters(Statistics, array())
#8
+
/var/www/html/limesurvey/application/controllers/AdminController.php(204): CController->run("statistics")
#9
+
/var/www/html/limesurvey/vendor/yiisoft/yii/framework/web/CWebApplication.php(282): AdminController->run("statistics")
#10
+
/var/www/html/limesurvey/vendor/yiisoft/yii/framework/web/CWebApplication.php(141): CWebApplication->runController("admin/statistics/sa/index")
#11
+
/var/www/html/limesurvey/vendor/yiisoft/yii/framework/base/CApplication.php(185): CWebApplication->processRequest()
#12
+
/var/www/html/limesurvey/index.php(161): CApplication->run()

20555: Separate Question Type and Question Theme Management

Mon, 08 Jun 2026 19:35:17 +0200

# Feature Request: Separate Question Type and Question Theme Management

## Summary

Question Type and Question Theme represent two different concepts and should therefore be managed independently within the LimeSurvey user interface.

Currently, the Question Theme is selected as part of the question type selection process. In addition, it is not possible to change the assigned Question Theme after a survey has been activated. This creates unnecessary restrictions and does not reflect the underlying data model.

## Background

LimeSurvey already stores these properties separately:

* `questions.type` defines the question type and its underlying data structure.
* `questions.question_theme_name` defines the assigned Question Theme.

This separation in the database indicates that Question Type and Question Theme are distinct entities with different responsibilities:

* **Question Type** determines behavior, answer structure, validation logic, and data storage.
* **Question Theme** determines presentation, layout, and user experience.

Because these concerns are different, they should also be managed independently in the user interface.

## Proposed Changes

### 1. Separate Question Type and Question Theme Assignment

Instead of selecting a Question Theme during question type selection, users should be able to:

1. Select the Question Type.
2. Independently select or change the Question Theme in a dedicated setting.

This would provide a clearer and more intuitive workflow and better reflect the underlying architecture.

### 2. Allow Changing the Question Theme After Survey Activation

Users should be able to change the assigned Question Theme for a question even after the survey has been activated, provided that the selected theme is compatible with the current question type.

Changing the Question Theme typically affects only the presentation layer and does not modify:

* the question type,
* the answer structure,
* the stored response data,
* ExpressionScript logic,
* SGQA identifiers,
* database schema.

Therefore, preventing all theme changes after activation appears unnecessarily restrictive.

## Benefits

* Better separation of concerns between functionality and presentation.
* User interface that reflects the existing data model.
* Greater flexibility when improving survey design after activation.
* Easier experimentation with different visual representations.
* Reduced need for workarounds or direct database modifications.

## Compatibility Considerations

To ensure safety, LimeSurvey could restrict post-activation theme changes to themes that are explicitly compatible with the current question type.

If a theme requires attributes or structures that are incompatible with the existing question configuration, LimeSurvey could display a warning or prevent the change.

## Conclusion

Question Types and Question Themes are already modeled as separate concepts in LimeSurvey. Allowing independent management of both, including post-activation changes of compatible Question Themes, would improve usability, flexibility, and consistency with the underlying architecture.

20553: 500 server error when survey is accessed directly via movesubmit parameter under PHP 8.x

Wed, 10 Jun 2026 18:41:36 +0200

When a survey is called directly with move=movesubmit in the URL (without going through the normal survey start flow), the session is never fully initialized. As a result, $_SESSION[$this->LEMsessid]['insertarray'] is null when setArgs() is called during the submit process.
Under PHP 7.4, in_array() accepted null as the second argument silently. Under PHP 8.x, this throws a fatal TypeError, causing a 500 Internal Server Error.
This affects installations where surveys are triggered externally via direct submit URLs, for example:
/index.php/survey/index?move=movesubmit&thisstep=0&sid=999991&token={TOKEN}&lang=en

This is a common use case in panel research workflows where respondents are redirected directly to a completion/screenout/quota-full survey without going through the normal survey navigation.

Root Cause:
In application/helpers/SurveyRuntimeHelper.php, line 692, $_SESSION[$this->LEMsessid]['insertarray'] is accessed without checking whether it is set:
php// Current code (line 692):
if ($this->LEMsessid && !in_array("refurl", $_SESSION[$this->LEMsessid]['insertarray'])) {
When the session has not been initialized through the normal survey flow, insertarray is null, causing the fatal error under PHP 8.x.

Proposed Fix:
Add an isset check before the in_array call:
phpif ($this->LEMsessid
&& isset($_SESSION[$this->LEMsessid]['insertarray'])
&& !in_array("refurl", $_SESSION[$this->LEMsessid]['insertarray'])) {
This is a minimal, non-breaking fix that makes the behavior consistent with how PHP 7.4 handled the same situation silently.

20552: With debug set and demoMode : reveive an error at end of survey with email notification

Fri, 05 Jun 2026 17:32:54 +0200

At end of survey : there a a PHPO warning about some data not set.

20551: Password requirement plugin settings are not apply

Fri, 05 Jun 2026 12:29:22 +0200

When you lower password requirement plugin about at least one uppercase character and set to NO
You can not create manually user without an uppercase character

20550: subquestion conditions do not work in mobile view

Fri, 12 Jun 2026 12:59:47 +0200

When using sub-question conditions within array(texts-) questions, they do not function correctly in the mobile view: In the mobile view, all sub-questions are displayed, even if the conditions for one or more of the sub-questions are not met.

20547: Version 6.17.5 is marked as unstable (incorrectly?)

Mon, 08 Jun 2026 19:18:16 +0200

On our self-hosted installs (verified on three different installs), a new LimeSurvey version 6.17.5 (260527) is offered, as a security update, but marked as unstable. On the release page, https://community.limesurvey.org/releases/, the version does not appear at all. Is this a new release candidate of 7.x that has been erroneously marked as 6.17.5?

20546: Error message 400:The CSRF token could not be verified

Wed, 03 Jun 2026 13:34:18 +0200

A participant of our survey got an error message and couldnt do the survey because of that. He is the only one (from who we know) with this error ( 400:The CSRF token could not be verified.).

20542: Upload question .question expression stay empty

Thu, 28 May 2026 18:42:24 +0200

In expressionmanager : variable $question is not set for file upload question

20541: LimeSurvey's 7.0.0 new editor gets stuck in loop on 'Create survey'

Wed, 17 Jun 2026 13:15:03 +0200

Hello,

I was in the process of manual installation of Lime Survey 7.0.0 on Alma Linux 8.10 with PHP 8.1, Apache 2.4, MYSQL 8.0.

However, post successful installation on selecting new Editor and trying to create survey it gets stuck on 'checking permissions' and doesn't move ahead.

I have attached the video of the same.

Also following is the console log from the browser :





XHRGET

http://{{URL}}/{{TO}}/{{LIME}}/rest/v1/user-detail/1

[HTTP/1.1 401 Unauthorized 164ms]



XHRGET

http://{{URL}}/{{TO}}/{{LIME}}/rest/v1/user-permissions

[HTTP/1.1 401 Unauthorized 169ms]



Object { name: "FCP", value: 1748, rating: "good", delta: 1748, entries: (1) […], id: "v5-1779951763573-3911806717833", navigationType: "navigate" }

57.038de187.js:1:917

Object { name: "TTFB", value: 1359, rating: "needs-improvement", delta: 1359, entries: (1) […], id: "v5-1779951763573-5896493810644", navigationType: "navigate" }

57.038de187.js:1:917

API Error: 

Object { code: "UNAUTHORIZED", message: "An unknown error occurred", httpStatus: 401, originalError: AxiosError }

index.64d8e7b8.js:1:2314

XHRGET

http://{{URL}}/{{TO}}/{{LIME}}/rest/v1/i18n/en

[HTTP/1.1 401 Unauthorized 164ms]



API Error: 

Object { code: "UNAUTHORIZED", message: "An unknown error occurred", httpStatus: 401, originalError: AxiosError }

index.64d8e7b8.js:1:2314

API Error: 

Object { code: "UNAUTHORIZED", message: "An unknown error occurred", httpStatus: 401, originalError: AxiosError }

index.64d8e7b8.js:1:2314

Source map error: Error: request failed with status 404

Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9



Resource URL: http://{{URL}}/{{TO}}/{{LIME}}/editor/build/static/js/async/57.038de187.js

Source Map URL: 57.038de187.js.map

Source map error: Error: request failed with status 404

Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9



Resource URL: http://{{URL}}/{{TO}}/{{LIME}}/editor/build/static/js/index.64d8e7b8.js

Source Map URL: index.64d8e7b8.js.map

Object { name: "LCP", value: 1767, rating: "good", delta: 1767, entries: (1) […], id: "v5-1779951763573-4952276506098", navigationType: "navigate" }

57.038de187.js:1:917

What could be the cause of this issue?.

20539: Theme editor option : no way to add help

Wed, 27 May 2026 15:18:35 +0200

In theme editor core option : there are no way to add help

20538: CU - Can't update to 6.17.5

Wed, 27 May 2026 14:29:29 +0200

Hi, when starting the CU for 6.17.5, the release notes are for 7.0.0-RC1

So either the release notes are just wrong or the update channel. However, I cannot continue the the update because I don't know which version will be installed.

Kind regards
Benny

20537: "Save and Create Next Question" button

Mon, 25 May 2026 02:29:32 +0200

When creating a survey question, would be nice if there was a "Save and Create the Next Question" button. I think it would be more functional than "Save and Close". Would save clicks. Thanks for considering.

20536: Subquestions don't display

Thu, 28 May 2026 10:46:32 +0200

I have two questions, [acneloc] and [acneprob]

[acneprob] only appears if two or more subquestions are checked in [acneloc].
[acneprob] uses array filtering to present only the subquestions that were checked in [acneloc].

When two subquestions are checked in [acneloc], [acneprob] successfully appears but not the subquestions.

20535: Example screenshot for "Image select multiple choice" is not actually of that question type

Sat, 23 May 2026 12:41:04 +0200

The sample screenshot for "Image select multiple choice" is incorrect, suggesting you can have text under images.

It is actually a screenshot of the standard multiple choice type.

Recording this issue after conversation on https://forums.limesurvey.org/forum/can-i-do-this-with-limesurvey/159383-having-text-under-images-when-using-image-select-multiple-choice

20534: Ability to have SVG logo on form

Sat, 23 May 2026 11:06:02 +0200

I want to be able to display an SVG logo on my survey.

While I can successfully upload and select an SVG logo, it does not render on the Fruity TwentyThree theme, with no error message to indicate failure either.

20533: Uploading an image in theme shows confirmation but the image does not appear in list until manual refresh

Sat, 23 May 2026 11:06:29 +0200

In Theme Options > Image
After uploading an image, the logo does not appear in the list, despite the success message and generally "live" nature of the interface. I would have expected it there.

Workaround is to do a manual refresh in the browser, at which point it will appear in the list.

20532: STARTPOLICYLINK and ENDPOLICYLINK return errors in the survey logic view

Tue, 02 Jun 2026 16:33:27 +0200

On Privacy Policy settings for surveys, the guidance states:

> If you want to specify a link to the privacy policy, set "Show privacy policy text with mandatory checkbox" to "Collapsible text" and use the placeholders {STARTPOLICYLINK} and {ENDPOLICYLINK} in the "Privacy policy checkbox label" field to define the link that opens the policy popup. If there is no placeholder given, there will be an appendix.

Adding these variables to the "Privacy policy checkbox label" page leads to an error in the Survey Logic view.

20530: Discrepency between $config['dbversionnumber'] and available helpers Update_xxx.php (6.17.4)

Fri, 22 May 2026 13:02:34 +0200

Since the update to 6.17.4, the package download config.php shows $config['dbversionnumber'] = 651;
However, there is no Update_651.php, and this is probably why the notification keeps on appearing?

Is the Update_651.php missing, or should the dbversionnumber be 650?

Currently, this results in repeated "Database updated from 650 to 650" messages in the admin panel.