LimeSurvey bugs and feature requests - Issues

20851: React editor Insert/edit link Tiny button label is untranslated

Tue, 10 Nov 2026 16:08:51 +0100

See screenshot below.

20850: Array dual scale Header 1 & 2 are untranslated

Tue, 10 Nov 2026 16:21:45 +0100

See screenshot below.

20849: No lss/lsa download archive button when selecting 250 or 500 surveys per page

Tue, 10 Nov 2026 09:41:55 +0100

The issue appears when trying to export lss/lsa files. After selecting surveys and clicking "export" the list of surveys appears but no download button is visible. The issue seems to only appear when selecting 250 or 500 surveys per page. Everything worked fine when I tested for 5, 10, 20, 50 or 100.

20847: Context change modal – Incorrect focus management

Mon, 09 Nov 2026 19:41:10 +0100

When submitting the form with one or more required questions left unanswered, a modal dialog is displayed to inform the user of the validation errors.

However, keyboard focus remains on the "Next" submission button, outside the modal dialog, instead of being moved into it.

Additionally, when the modal is closed, focus is not automatically returned to the first required field that has not been completed.

This makes navigation more difficult for keyboard and screen reader users.

20846: Fruity theme corner radius active setting icon is not visible with Classic editor and Sea Green admin theme

Mon, 09 Nov 2026 17:07:43 +0100

See screenshot below.

20845: MC question with Other option - interference with condition

Mon, 09 Nov 2026 12:26:15 +0100

I am experiencing an issue with conditional question display
I have created a multiple-choice questions with the built-in Other option activated.
The question is only supposed to appear when a specific condition is met
However, the entire question appears regardless of whether the condition is fulfilled.

I suspect this might be related to the activation of the built-in Other option

Is there a known issue with conditional display when using multiple-choice questions with the built-in Other option?

Are there any known configuration issues or workarounds that could resolve this behaviour?

I am attaching a simple survey structure where I have isolated the problem
first question is used to build the condition on
second (with other option) and third questions (without other option) are both MC questions, and are conditionned to only appear if a certain answer is chosen in the first question

20844: Make React editor feedback button optional

Mon, 09 Nov 2026 09:01:09 +0100

In SideBar.js, showFeedbackButton is a boolean indicating whether or not the feedback button should be rendered on the React editor sidebar. Currently this is hardcoded to true.
Perhaps it would be useful to have a global setting for disabling the button?

20840: New editor: answer option and subquestion codes can not be edited on an active survey

Sun, 08 Nov 2026 09:57:43 +0100

In the new editor, once a survey is active, the codes of answer options and subquestions are shown as read-only text, Add answer / Add subquestion is disabled with the tooltip "Deactivate survey to edit", and the remove button is hidden. The classic editor allows editing answer option codes of an active survey, and this should be possible in the new editor too.

Code (editor/src):
- components/QuestionTypes/subquestionCodeComponents.js, SubquestionCodeInput: renders a plain div instead of the input when isSurveyActive.
- components/QuestionTypes/QuestionModes/OptionQuestionEditMode.js lines 105, 122, 195, 205: remove button hidden, add button disabled when isSurveyActive.
- Same in the Cloud editor (editor/core f4c0b93f).

20837: New editor: images uploaded for answer options are broken when LimeSurvey is installed in a subfolder

Sat, 07 Nov 2026 23:00:52 +0100

When LimeSurvey is installed in a subfolder (e.g. https://example.com/limesurvey/), pictures uploaded in the new editor (e.g. for the List image select (Radio) / Image select multiple choice themes: click or drag a picture onto an answer option) are saved with a root-relative path such as /upload/surveys//images/picture.png. The browser resolves this to https://example.com/upload/... instead of https://example.com/limesurvey/upload/..., so the picture is broken in the editor preview and in the survey.

The REST endpoint v1/file-upload-survey-image returns both uploaded.filePath (relative to the LimeSurvey root, without the base URL: FileUploadService::convertFullIntoRelativePath()) and uploaded.fileUrl (with App()->getBaseUrl(true)). The stored path is the one without the base URL.

On an installation in the web root the problem doesn't show, because the root-relative path happens to be correct.

20835: New editor: 'Detailed admin notifications email address' is locked on active surveys, but the basic address is not

Sat, 07 Nov 2026 22:16:22 +0100

In the new editor's Notifications & data settings, the field 'Detailed admin notifications email address' (EMAIL_RESPONSE_TO in getNotificationsDataSettingsBlocks.js) has activeDisabled: true, so it can't be changed while the survey is active. The basic admin notification address has no such lock, and in the classic editor neither address is locked.

The address only controls where notification emails go, so there is no reason to lock it on an active survey. The 'Send detailed admin notifications' toggle is not locked either, which makes the behaviour inconsistent.

20833: New editor: '... > View > Question codes' changes the survey setting, so participants see question numbers and codes

Sat, 07 Nov 2026 22:16:21 +0100

In the new editor, the top bar menu '...' > View > 'Question codes' looks like an editor display option. But the toggle writes the survey setting showqnumcode (TopBarActions.js handleToggleQuestionCodes, converted by TransformerInputSurvey convertShowQNumCode): turning it on sets 'Question number and code' to B (show both), turning it off sets X (hide both).

As a result participants see the question number and code in front of every question (e.g. '1 age') once an administrator only wanted to see the codes while editing. Turning it off also overwrites a previously chosen setting such as 'Show number only'.

20830: New editor: after changing the question type, deleted answer options are still shown until reload

Sat, 07 Nov 2026 19:44:35 +0100

When you change the type of a question in the new editor, the server deletes all answer options of the question (QuestionService::updateQuestionData() calls removeAnswersAndDependentConditions() on every type change), even between types that both use answer options, e.g. List (radio) -> List (dropdown).

The new editor does not reflect this: the question card still shows the old answer options after the type change. They only disappear after reloading the page. The user believes the answer options were kept, and any further edits to them are made on options that no longer exist.

20828: Numeric Multiple with total A11Y issue

Fri, 06 Nov 2026 18:40:18 +0100

Numeric multiple choice” component – Status message not announced

The area displaying the totals and the remaining number is not announced by screen readers when entering responses, because this dynamic area does not have an aria-live attribute.

To fix: Add the attributes aria-live="polite" and aria-atomic="true" to the containers of these areas.

WCAG 2.1 – Critère de succès 4.1.3 : Status Messages (AA).

20827: Survey save state always uses 12h format

Fri, 06 Nov 2026 16:26:51 +0100

On line 218 in editor/src/components/wrappers/SurveyLogicProvider.js the format is set to 'hh:mm'.
This misleading in two ways: 1) it doesn't specify AM/PM and 2) because of 1) the user might think that the 24h format is used while that's not the case. I think the time displayed should either be in 24h format or be based on a user setting.

20826: New LimeSurvey editor - 400 error

Fri, 06 Nov 2026 15:06:50 +0100

Hello,
I migrated from LimeSurvey version 6.10.17 to the latest version, 7.9.1. I have encountered a troublesome bug—one that I was unable to reproduce on the LimeSurvey demo instance.
However, I was able to reproduce it using a fresh installation on my development server.

The error occurs in version 7.0.5 and later.

Environment:
RockyLinux
Apache 2.4.X
PHP 8.4.27
PostgreSQL 17.9
RewriteEngine On

Contents of the config.php file: (actual address modified)
// Enforce a certain URL base
'request' => array(
'hostInfo' => 'https://limesurveyV7-dev.org'
),

'urlManager' => array(
'urlFormat' => 'path',
'rules' => array(
// You can add your own rules here
),
'showScriptName' => true,
),

The access URL appears in the browser for a few seconds, then is replaced by a "short URL" (as described in the manual here: https://manual.limesurvey.org/General_FAQ#How_can_I_remove_index.php_from_the_URL_path_to_get_a_shorter_URL).

However, I haven't actually configured a short URL (if I set that option to 'False', everything stops working, except for the homepage).

The same issue occurs if I perform a migration and try to access an existing questionnaire (see the video—I’m attempting to post it here, though I’m not sure if it will go through; I’ll also provide a Google Drive link as a backup, just in case—@Denis?).

It looks somewhat similar to this bug: https://bugs.limesurvey.org/view.php?id=18383

20825: "Token length must be at least 5" error message is untranslated

Mon, 09 Nov 2026 10:11:43 +0100

On line 127 in editor/src/components/SurveySettings/Settings/getParticipantsSettingsBlocks.js.

20822: Various strings for statistics are unstranslated

Fri, 06 Nov 2026 14:41:25 +0100

To name a few: Male, Female, Yes, No, No answer, 1st, 2nd…, hours ago. Please see the screenshots below.

20820: HTTP 500 error when quota_exit is triggered in surveys migrated from LimeSurvey 5.6.x to 7.x

Fri, 06 Nov 2026 10:56:46 +0100

After migrating from LimeSurvey 5.6.x to LimeSurvey 7.x, some migrated surveys return an HTTP 500 Internal Server Error when a quota is reached and quota_exit is triggered.

The survey works normally until the quota condition is reached.

When the quota is triggered, instead of displaying the configured quota exit message/page, LimeSurvey returns an HTTP 500 Internal Server Error.

The issue appears to affect surveys migrated from LimeSurvey 5.6.x to LimeSurvey 7.x.

20818: Mandatory means different things per question type and can conflict with the minimum/maximum answers settings

Thu, 05 Nov 2026 21:51:43 +0100

This has been confusing survey authors for years. Since 2019 the same kind of report keeps coming back: a mandatory question can't be completed, or the minimum/maximum answers setting seems to be ignored (15363 in 2019, 17330 in 2021, 20622 in 2026). Each time only the reported case was patched, and only for ranking. The underlying inconsistency was never addressed, so every other question type with more than one answer still has the same problem.

The "Mandatory" setting is one On/Soft/Off switch, but what it requires depends on the question type, and the question editor doesn't show which rule applies:

- Single-answer types (list, text, numerical, date, ...): an answer must be given.
- Multiple choice (with and without comments): at least one option must be checked.
- All array types, multiple short text, multiple numerical: every row must be answered.
- Array (Numbers) with checkbox layout: at least one box per row.
- Ranking: all items must be ranked, unless a minimum or maximum number of answers is set. Then one ranked item is enough.

The "Minimum answers" and "Maximum answers" settings work separately from mandatory, which causes three problems:

1. Questions that can't be completed. If a mandatory array, multiple short text or multiple numerical question has a maximum number of answers below its number of rows, it can never be completed. Mandatory requires all rows, and the maximum allows fewer. Ranking had the same problem (15363, 17330); it was fixed with a special case for ranking only.
2. A minimum that has no effect. On a mandatory array, "Minimum answers = 3" does nothing, because all rows are required anyway.
3. A hidden mandatory. A question that isn't mandatory but has a minimum number of answers can't be left empty. The sum settings of multiple numerical behave differently: they only apply once the question has been answered.

20811: file upload mandatory doesn't block saving

Tue, 03 Nov 2026 13:17:50 +0100

Hi,
in a survey, If I upload a file and then I remove it, even if question is mandatory I'm still able to save the answer
in responses table I saw that if the field contains [] instead of null, the answer can be saved.

20809: Multiple choice with other : add an option for Cother

Mon, 09 Nov 2026 12:30:22 +0100

There are a new database option for Multiple choice with other
It's great , a lot of user can be happy but

It can be great to have it in options

_Save Y for other_ on/off for the sample : i use `save_other_checkbox`

1. on by default (1)
2. With [readonly_when_active](https://github.com/LimeSurvey/LimeSurvey/blob/359ccdc3a6d9c9704470ac056afa272e1e31ba6f/application/extensions/AdvancedSettingWidget/AdvancedSettingWidget.php#L57) to true
3. Set `save_other_checkbox` to 0 for all existing multiple-choice questions in the activated survey.
4. Check DB after import LSA to set `save_other_checkbox` to 0 or not

20808: Participant tokens not marked as completed (Completed? remains -) in Tokens table upon final survey submission

Thu, 29 Oct 2026 09:35:33 +0100

In a closed-access survey using tokens with "Enable participant-based response persistence" turned ON and non-anonymized responses, submitting the completed survey correctly flags the entry in the Responses table (showing green checkmark). However, it fails to update the Completed? status in the Participant Table (Tokens), leaving it empty (-).

Furthermore, when Uses left is set to 1, opening the survey link prematurely decrements Uses left to 0 before submission, blocking the user from resuming their session from another browser/device. Manually increasing Uses left allows re-entry, but upon final submission Uses left simply decrements (e.g., from 3 to 2) without ever updating Completed?, causing total status desynchronization between the responses table and the participant table.

20806: Position of other option: "before answer option/subquestion"

Wed, 28 Oct 2026 16:25:49 +0100

Currently there is the option to position the "other" field after a specific subquestion or answer option. There should be an option to position it BEFORE a subquestion/answer option.

20804: 7.8.0 : WCAG failed Success Criterion 3.2.2 On Input for Multiple checkbox

Mon, 09 Nov 2026 12:29:20 +0100

There are a context update without any information to user

20802: Passthru in End Url gives error in Survey Logic File

Tue, 27 Oct 2026 11:23:58 +0100

Passthru in End Url gives error in Survey Logic View

Example URL: https://localhost/return?subjectid={PASSTHRU:subjectid}

gives an error alike:

End URL: - https://localhost/o4u_drupal/return?subjectid=PASSTHRU : subjectid

As the curly brackets seem to have been lost during creating of the Survey Logic View