LimeSurvey bugs and feature requests - Issues

20657: dsgfsghr

Thu, 20 Aug 2026 07:13:26 +0200

rggr

20656: fdgdfg

Thu, 20 Aug 2026 07:10:59 +0200

dfgdfg

20655: Dialog for informing users about soft required questions is confusing

Wed, 19 Aug 2026 17:09:21 +0200

I've been using Dutch and Dutch informal, and the (default) translation for the dialog that informs users about an open question with requirement = soft is confusing.
There are 2 problems that i believe anyone using dutch would have:
* both versions of dutch have a question text that means something different: the dutch version asks the user to fill in the question if possible before continuing, while the informal version says that you cannot continue without answering the question (which is just not true).
* The 2 buttons have labels that are very difficult to interpret what they actually mean. The button labels translate to "Continue answering" (intended as, skip the soft required questions and continue with the rest of the survey) and "Answer question" (go back and answer the soft required question anyway). I would be very confused to decide which of the 2 buttons to click.
For completeness, see attached screenshots of the dialog

Proposal texts for Dutch:
* question: Een of meer verplichte vragen zijn niet beantwoord. Vul deze, indien mogelijk, alsnog in voordat u verder gaat met de vragenlijst.
* Change button "Met beantwoorden doorgaan" (continue with rest of the survey) to "Verdergaan met de vragenlijst"
* Change button "Vraag beantwoorden" (answer the required questions) to "Vragen alsnog beantwoorden"

Proposal texts for Dutch informal:
* question: Een of meer verplichte vragen zijn niet beantwoord. Vul deze, indien mogelijk, alsnog in voordat je verder gaat met de vragenlijst.
* Change button "Met beantwoorden doorgaan" (continue with rest of the survey) to "Verdergaan met de vragenlijst"
* Change button "Vraag beantwoorden" (answer the required questions) to "Vragen alsnog beantwoorden"

20653: Listing submitted responses for surveys take LOTS of time

Tue, 18 Aug 2026 22:20:19 +0200

Browsing survey responses (Responses → Browse responses) is extremely slow for surveys with a non-trivial number of questions and responses, because `getExtendedAnswer()` in `application/helpers/common_helper.php` runs a full, unfiltered `SELECT * FROM questions WHERE sid = :sid` query **on every single rendered cell** of the responses grid, in addition to a `Survey::model()->findByPk()` query per cell. For a page of 10 responses × ~80 columns this adds up to 500+ avoidable queries per page load, and is the dominant cost of the page.

20649: API feature request: expose survey activation consistency check without activating

Wed, 12 Aug 2026 21:38:42 +0200

We are integrating with LimeSurvey through the RemoteControl API and we would like to request an API capability to validate whether a survey is activation-ready, without actually activating it.

Current problem:
At the moment, consistency validation appears to happen only when calling activation-related actions (for example activate_survey). This makes it hard for external tools to provide clear pre-activation guidance to users.

Requested capability:
Please expose a dedicated API method to run the same consistency checks used by activation, but in read-only mode.

Suggested endpoint behavior:

Input: survey_id
Output:
* is_consistent (boolean)
* errors (list of blocking issues)
* warnings (list of non-blocking issues)
Optional structured details per rule, for example:
* no question groups
* no questions
* no active questions
* groups without questions
* other activation blockers detected by core LimeSurvey logic

Why this helps:

External dashboards can show users exactly what must be fixed before activation.
Integrations can avoid failed activation attempts.
Better UX and fewer support issues for admins.
Backward compatibility:

New method can be additive and optional.
Existing activation flow remains unchanged.
Thanks for considering this request.

20645: Fruity theme hides selected value in Bootstrap Select dropdown on hover

Mon, 10 Aug 2026 18:00:14 +0200

When using a Bootstrap dropdown (Type: !) in the Fruity theme, the selected answer becomes invisible while the mouse cursor is hovering over the dropdown.

The selected value is still present in the DOM and the Bootstrap Select component retains the correct value. However, the value is not visually displayed while the dropdown button is in its hover/focus/active state.

As soon as the cursor is moved away from the dropdown, the selected value becomes visible again.

(attached is a video of the behavior and a .lss file)

20639: Outdated Documentationx, please advise

Thu, 06 Aug 2026 15:49:21 +0200

We are trying to follow the steps in https://www.limesurvey.org/manual/Installation_security_hints#The_access_to_the_config.php_file

As it turns out, the settings we are supposed to change are no longer located in the config.php file, but can be found here:

limesurvey/application/config/internal.php: 'basePath' => dirname(dirname(__FILE__)),

limesurvey/application/controllers/InstallerController.php: ."\t" . "'runtimePath' => dirname(dirname(dirname(__FILE__))).DIRECTORY_SEPARATOR.'tmp'.DIRECTORY_SEPARATOR.'runtime'," . "\n"

limesurvey/application/config/internal.php: 'rules' => require('routes.php'),

So do they need to be changed at all?
Or can config.php now be moved out of the directory tree with no further changes and a simple

in the placeholder file?

Kindly update your documentation.

20638: Theme options dropdowns do not have any values in Firefox

Wed, 12 Aug 2026 14:17:44 +0200

In the Firefox browser only, the theme options values. These do render on Chromium.

I identified this in all "Theme optiosn"select boxes (e.g. "Theme colors", "Fonts", "Check icon").

All of these work as expected in Chromium-based browsers.

If you switch to Chromium you can edit these values.
Firefox will display the selected values when refreshing the page, but still doesn't give any items in its own dropdown, making it impossible to change the setting through firefox.

20637: 500 Internal Server Error since Update

Fri, 07 Aug 2026 14:53:21 +0200

Lime is very slow and i do not get new answers by participants. When I try to download the dataset for spss or excel i get the error "500 Internal Server Error". We had an update yesterday and i believe that we have the problems since then. Yesterday everything worked fine.

20630: Renaming a parent custom theme breaks child theme inheritance and leaves stale parent references

Thu, 13 Aug 2026 16:56:58 +0200

When a custom theme that serves as the parent of another custom theme is renamed, any child themes that extend it continue to reference the original parent theme internally, even though the Theme Editor overview displays the parent's new name.

As a result, the child theme can no longer resolve inherited assets and becomes unusable in the Theme Editor. Attempting to edit, duplicate, extend, or reinstall the child theme results in errors indicating that inherited files or the parent theme cannot be found, even though the parent theme still exists under its new name.

20626: Bounce tracking freezes at latest 6.x and 7.x version

Thu, 06 Aug 2026 09:08:05 +0200

At the latest LimeSurvey 7 version when I'm starting the bounce processing at my surveys, the screen just freezes and a pop-up shows. I can neither click any button nor return to the previous page. I need to fully reload the screen.

It looks like the script fully crashes. The console does not show any errors.

The popup interface problem shows at the latest 6.x AND 7.x version.

I define bounce settings globally and at my survey selected "Use global settings".

20624: DB crash when updating from 7.0.5 to 7.0.7 due to missing DB version check

Fri, 14 Aug 2026 17:08:23 +0200

While upgrading **LimeSurvey 7.0.5** to **7.0.7**, we encountered a database update failure on a server running **MariaDB 10.1.48**.

As a temporary workaround, we were able to complete the update by changing the column type from `JSON` to `LONGTEXT` in:
`application/helpers/update/updates/Update_709.php` (line **19**)

```php
addColumn("{{responses_" . $sid . "}}", "Q{$parent_qid}", "LONGTEXT");
```

However, we believe the actual issue is that the updater starts the database migration without first verifying that the database server meets the documented minimum requirements.

20619: Security update available - although LimeSurvey is updated to the latest 6.x version

Sat, 08 Aug 2026 13:23:50 +0200

We currently have two recent versions, one in the 6.x line and one in the 7.x line. Both are considered stable.
Since we cannot switch to the 7.x version anytime soon, but security updates are available for the 6.x version, the message “Security update available” should only be displayed if not all security patches for the 6.x version have been installed.

This leads to uncertainty and unease among users, as this gives the impression that LimeSurvey is being operated with security vulnerabilities, while at the same time handling sensitive data (surveys).

20611: New feature to exclude items at quick translation

Thu, 06 Aug 2026 14:38:28 +0200

The quick translation feature is a very useful tool, especially when making use of a Google Translate API key to automatically translate items to different languages. There are some drawbacks though: When using the auto-translation, it always adjusts all items on the current page/tab. But if parts of the translation have already been reviewed by a native speaker, or if there are equation questions, which the auto-translate sometimes messes up, then you need to redo the whole translation process after the auto-translation was done.

This can easily be solved by having a checkbox for every item, which is enabled by default, but offers the ability for the user to disable the translation feature for certain items.

We could try to develop this and provide a pull request. Is this considered a helpful feature? Then we would give it a try.

20608: datasecurity_notice_label is not rendered correctly with "Collapsible text" and "All in one" survey format

Fri, 17 Jul 2026 14:04:12 +0200

This is a follow up for 19852.

20605: Non consistent branch label

Tue, 21 Jul 2026 18:05:02 +0200

In the Comfort Update screen, the message says there is an unsable update but actually it is a stable one.
See screenshot

20600: When try to create dummy participant : page must be reloaded

Thu, 13 Aug 2026 16:58:25 +0200

When try to create dummy participant, if you don't reload the page, no action is done when you clickthe 1st time
This happen with mandatory attribute.

20599: When questions have a relevance equation, mandatory questions are not enforced.

Thu, 09 Jul 2026 08:57:18 +0200

I am seeing issues in a survey, where I have mandatory questions, and I am able to move forward without answering them
The issue seems to happen when questions have a relevance equation... that seems to kill the enforcement of mandatory questions.
When the questions don't have relevance equations, the mandatory rule is enforced.

This happens on v6 and v7

20598: Token overwrite when opening multiple survey tokens in different tabs of the same browser

Thu, 09 Jul 2026 12:35:34 +0200

When a user opens two distinct token links for the same survey in two different tabs of the same browser session, LimeSurvey overwrites the active token session data with the most recently loaded one. If the user goes back to the first tab and tries to save or proceed, the response data gets cross-contaminated or associated with the second token.

20596: Panel-Integration parameter (Survey-URL-Parameter) missing after copy

Tue, 21 Jul 2026 18:10:46 +0200

When I copy a survey, the panel integration parameters are missing in the result.

When using export / import to "copy" a survey, the panel integration parameters are not missing.

20595: Printable Survey not showing "other", after importing via txt

Mon, 06 Jul 2026 12:03:24 +0200

After importing a Survey via txt the "export" -> "Printable Survey" view does not show any other fields.
A workaround for this is: After importing open every question containing an other field, then saving the question (without any changes).
It seems as if saving the questions changes some parameter in the background, which is necessary for the Printable survey view.

Also it seems that the issue:
only occurs on txt import
applies to all question that have a built in other field option
is unaffected by other position and custom text

20589: Direct link to view single response no longer opens a dedicated page since v7 — only a modal/popup, breaking shareable links

Fri, 07 Aug 2026 09:48:14 +0200

## Expected Behavior

In previous LimeSurvey versions (pre-v7), clicking view/edit on a response opened a dedicated page with its own unique URL, e.g.:

https://umfrage.example.tld/responses/view?surveyId=532561&id=280

This URL was directly shareable, colleagues or reviewers could be sent a link straight to a specific response without needing to log in, navigate to the survey, and manually search for the response ID.

## Problem

* Old-style direct links (responses/view?surveyId=X&id=Y) still resolve to a working page (confirmed on our instance), but this is no longer reachable from the UI itself.
* The response list now only supports a popup for viewing/editing individual responses, and popups cannot be bookmarked, linked, or shared via URL.
* This breaks existing workflows for teams that share direct links to specific responses (e.g. for QA, moderation, or cross-referencing with partners).

## Suggested Fix

Restore the option to open a response in its own dedicated page (either as default behavior or as a user-selectable alternative to the popup), so the URL updates to reflect the currently viewed response and can be copied/shared.

Alternatively: make the popup update the browser URL (e.g. via history.pushState) so the current response state is reflected in a shareable link, similar to how many modern SPA implementations preserve deep-linkability even inside modals.

20578: Survey activation fails when a survey contains a Ranking question due to a consistency check error indicating missing answer opt

Tue, 30 Jun 2026 12:09:37 +0200

Activating a survey containing a Ranking question triggers a consistency check error stating that the question has missing answer options, preventing the survey from being activated.

20576: Partial Scoring for Multiple Choice Questions

Fri, 26 Jun 2026 09:35:03 +0200

Currently, LimeSurvey calculates the score for Multiple Choice questions by summing the assessment values of all selected answer options. As a result, it is not possible to implement a scoring model that is commonly used in knowledge and competency tests.

In many tests, only correctly selected answers should contribute to the score, while incorrectly selected answers should neither receive points nor cause a penalty.

This behavior cannot currently be achieved using the standard Assessment feature.

If incorrect answers are assigned an assessment value of 0, participants can simply select all answer options and still receive the maximum score. Assigning negative values to incorrect answers introduces a penalty-based scoring system, which is not appropriate for many assessment scenarios.

20573: Database : ranking question contains unrelated information

Mon, 29 Jun 2026 17:21:21 +0200

In 7.X database contains the question ID and subquestion ID

But data are related to other subquestion ID