LimeSurvey bugs and feature requests - Issues

20786: Popup editor mode : no action with new editor

Wed, 21 Oct 2026 12:26:47 +0200

Popup editor mode or text editor mode : no action with new editor

20785: Popup dialog text edition too small

Wed, 21 Oct 2026 12:13:37 +0200

When using Popup dialog : height is to small : need to move down for some tools

20784: Add or move to dialog editor

Wed, 21 Oct 2026 12:13:37 +0200

User can use Pop-up HTML editor, which is better than copy/paste from Word, for example.
Admin user can set it as default

But the new windows are not clean enough (and there are size issue)
We already have dialog in quick translation: maybe we can add it as new setting ?

20783: When upload a forbidden extension with debug 7 : recive 500 error

Wed, 21 Oct 2026 12:05:27 +0200

When debug set :
htmlentities(): Passing null to parameter #2 ($flags) of type int is deprecated
/media/shnoulle/data/www/master/assets/packages/kcfinder/core/class/browser.php(922)

20781: Advanced Ranking SC 1.4.10 Reflow (Level AA) issue

Wed, 21 Oct 2026 11:32:15 +0200

There is an issue with advanced ranking when updating window size with advanced ranking
https://www.w3.org/WAI/WCAG21/Understanding/reflow.html

Max-width is not resetted

20780: Texts that depend on a number can only be translated with two forms, so languages like Polish or Czech show wrong grammar

Tue, 20 Oct 2026 17:48:52 +0200

Texts that change with a number (for example "1 file" / "5 files") can only be translated with a singular and a plural form. Many languages, such as Polish, Czech, Russian or Arabic, need more forms, so these texts show wrong grammar for many numbers. The new survey editor has the same problem.

20778: Configurable default values for notification fields (admin, adminemail, bounce_email) at survey creation

Tue, 20 Oct 2026 12:03:05 +0200

Currently, when a new survey is created, the three notification fields below inherit their
values from the parent survey group (or from the global defaults). There is no built-in way
to define what those defaults should be, nor to auto-fill the bounce address from the survey
owner's email.

We would like to be able to set, per instance (or per survey group), the following defaults
applied automatically to every newly created survey:

1. "Administrator" (admin) -> Inherit: OFF, field left empty
2. "Administrator email" (adminemail) -> Inherit: OFF, field left empty
3. "Bounce email" (bounce_email) -> auto-filled with the survey owner's email address
(Inherit: OFF)

Motivation / Use case
---------------------
We manage many surveys, each owned by a different person. We want bounce/delivery-error
notifications to go directly to the survey owner, without having to manually edit the
"Notification & data management" tab of every single survey after creation. Today this is a
repetitive, error-prone manual step: if an administrator forgets to switch "Inherit" off and
to set the correct bounce address, error notifications silently go to the wrong recipient (or
to the global admin), which can mean lost feedback and undetected invalid addresses.

Desired behaviour
-----------------
At survey creation (UI and RemoteControl2 API), the three fields above should be initialized
from a configurable default policy rather than blindly inheriting:

- a global / per-group setting defining the default state of inheritan, inheritema,
inheritbnc and the default content of admin / adminemail / bounce_email;
- a special token/placeholder (e.g. {owner_email}) usable as the default for bounce_email,
resolved to the email of the user who owns the survey (users.email of owner_id).

Proposed implementation (suggestions, not prescriptive)
-------------------------------------------------------
- Add new global settings in the "Global survey settings" panel for the three fields.
- When a survey is created, apply these defaults instead of pure group inheritance.
- Support a {owner_email} placeholder for bounce_email, resolved at save time from the
owner's account.

20777: Attempting to duplicate a question group on a active survey causes an error

Mon, 19 Oct 2026 17:16:59 +0200

20776: Survey question group settings are untranslated

Mon, 19 Oct 2026 13:27:59 +0200

20766: Error when running a different survey, upon closing the current one

Wed, 14 Oct 2026 14:25:58 +0200

The error described below blocks blocks the system for the user until session ends. It occurs both for admins and users working on subsequent surveys.
Re-opening the crashed survey or admin panel on a private window works.
Note: Looking at the cookies, the Session-ID changes every time a different survey is started. The error appears only after switching page from the welcome to another one.

20761: MS-SQL Survey activation can remove unique index on response table

Mon, 12 Oct 2026 18:18:31 +0200

With MS-SQD : there are potential issue about the unique index in response table.
Sometimes receive an SQL error about a duplicate index after survey is activated: "duplicate index on INDEX_1234 ..."

20760: All-in-one survey: question stays visible after an answer change although the question group it depends on is hidden

Sat, 10 Oct 2026 08:42:20 +0200

In an all-in-one survey, a question whose condition uses a question from a later question group can stay visible after the participant changes an answer, even though that later group is hidden. The question only hides again after another answer change. If the participant fills it in, the answer is dropped on submit.

20751: Unclear error message when re-using existing survey alias

Tue, 06 Oct 2026 12:54:39 +0200

When you set a survey alias and then use that same alias for a different survey, there is an unclear error message

20737: Index with question by question mode visually roken + usage of nav

Tue, 29 Sep 2026 12:48:15 +0200

With vanilla: the index is visually broken, and don't use nav and navigation

20736: Better difference between No response and not activated

Wed, 21 Oct 2026 11:38:17 +0200

In survey listing : difference between "No response" and "No response tables" is unclear.

20729: Calling export_responses over JSON-RPC with sDocumentType = "csv" always returns HTTP 500 with a TypeError.

Sun, 11 Oct 2026 06:00:05 +0200

Calling export_responses over JSON-RPC with sDocumentType = "csv" always returns HTTP 500 with a TypeError. The same call with "json" or "xls" succeeds on the same survey, same session and same user. CSV export from the admin web UI also works. The problem was already present on 6.x and persisted after upgrading to 7.3.0.

When EXPORT_FORMAT is "xls" or "json" works fine, when "csv" it errors. R code that produces error in step export_b64 <- ls_call:

ls_call <- function(method, params) {
body <- jsonlite::toJSON(list(method = method, id = 1, params = params),
auto_unbox = TRUE)
resp <- httr::POST(LS_API_URL, httr::content_type_json(), body = body)
if (httr::http_error(resp)) {
# Server-side failures put the actual reason in the body, usually as an
# HTML error page -- strip the markup and show just the readable text
txt <- httr::content(resp, as = "text", encoding = "UTF-8")
txt <- gsub("(?is)<(head|script|style)\\b.*?", " ", txt, perl = TRUE)
txt <- gsub("<[^>]+>", " ", txt)
txt <- trimws(gsub("\\s+", " ", txt))
stop(method, ": HTTP ", httr::status_code(resp), "\n", substr(txt, 1, 2000))
}
out <- jsonlite::fromJSON(httr::content(resp, as = "text", encoding = "UTF-8"))
if (!is.null(out$error)) stop(method, ": ", out$error)
if (is.list(out$result) && !is.null(out$result$status)) {
stop(method, ": ", out$result$status)
}
out$result
}

session_key <- ls_call("get_session_key", list(LS_USER, LS_PASSWORD))

export_b64 <- ls_call("export_responses", list(
session_key, survey$survey_id, EXPORT_FORMAT, survey$lang,
COMPLETION, HEADING_TYPE, RESPONSE_TYPE
))

So exporting in xls is the workaround, but given that csv is the standard for data exchange, it would be good to get the "csv" format working.

20726: Question attributes diverge between React editor and classic editor

Thu, 24 Sep 2026 21:36:11 +0200

This is a problem as fixes don't reach both editors. In some instances it is even worse as different question attributes are attributed to different question themes. For example this blocks a fix for 18721

20725: New Question-Editor - missing button/possibility to manual "Data Entry"

Thu, 24 Sep 2026 17:57:30 +0200

In the new (!) question editor i can't see a button or possibilty to enter the page "data entry" in a running survey in the category "results".
Even not in the "..."-menus.

20724: Page to define or import label sets is not reachable

Fri, 25 Sep 2026 08:30:13 +0200

Page to define or import label sets is not reachable.

20722: When check data integrity : if you have a old response table : it broke

Thu, 24 Sep 2026 17:59:53 +0200

When there are old response table data inetgrity result throiw a DB error

20718: error trying to update to 7.2

Wed, 23 Sep 2026 10:39:47 +0200

Call to undefined function getHtmlLangAttributeValue()

/var/www/limesurvey7/application/core/LSETwigViewRenderer.php(690)

678 // (in the future, should be template dependant done via XML file)
679 $aData["aSurveyInfo"] = array_merge($aData["aSurveyInfo"], $oTemplate->getClassAndAttributes());
680
681 $languagecode = App()->getLanguage();
682 if (!empty($aData['aSurveyInfo']['sid']) && Survey::model()->findByPk($aData['aSurveyInfo']['sid'])) {
683 if (!in_array($languagecode, Survey::model()->findByPk($aData['aSurveyInfo']['sid'])->getAllLanguages())) {
684 $languagecode = Survey::model()->findByPk($aData['aSurveyInfo']['sid'])->language;
685 }
686 }
687
688 $aData["aSurveyInfo"]['languagecode'] = $languagecode;
689 /* Separate from 'languagecode' since some codes (e.g. 'nl-informal') are not valid values for the HTML lang attribute */
690 $aData["aSurveyInfo"]['htmllanguagecode'] = getHtmlLangAttributeValue($languagecode);
691 $aData["aSurveyInfo"]['dir'] = (getLanguageRTL($languagecode)) ? "rtl" : "ltr";
692
693 if (!empty($aData['aSurveyInfo']['sid'])) {
694 $showxquestions = App()->getConfig('showxquestions');
695 $aData["aSurveyInfo"]['bShowxquestions'] = ($showxquestions == 'show' ||
696 ($showxquestions == 'choose' && !isset($aData['aSurveyInfo']['showxquestions'])) ||
697 ($showxquestions == 'choose' && $aData['aSurveyInfo']['showxquestions'] == 'Y'));
698
699
700 // NB: Session is flushed at submit, so sid is not defined here.
701 if (
702 isset($_SESSION['responses_' . $aData['aSurveyInfo']['sid']]) &&

20715: Create 2 other ranking system with the same views ?

Mon, 21 Sep 2026 12:26:50 +0200

New ranking system can be interesting to have 500 items ranked, but it doesn't interesting if we rank only 2 or 3 items for analysis.
Maybe we need 3 ranking question type

1. The new one
2. The old (6.X) one
3. One with one column by choice and save the rank (see https://demo.sondages.pro/714997)

20714: Ranking questions export is not user-friendly

Tue, 22 Sep 2026 10:35:54 +0200

When exporting ranking-type questions, there is a need for a more usable export format.

20709: Could not Download All Files via selecting with one click

Mon, 21 Sep 2026 21:59:28 +0200

In new UI's Results/Responses list when I tried to Download all attached files to that survey via clicking the select all button in header and click Download files below system gives error: "No files to download!"

20708: Concurrent response creation for the same participant

Sat, 19 Sep 2026 18:18:00 +0200

With long survey and some slow servers, there are multiple creations for one particpant.
It can happen too on limesurvey hosting