LimeSurvey bugs and feature requests - Issues

20800: Timestamps stay at 1980-XX if the survey is anonymous even if I explicitly chose to save timestamps at activation

Mon, 26 Oct 2026 15:09:17 +0100

We updated our instance from the last 6X to 7.7 and we have this bug :
- if I chose to save timestamp but select "yes" to anonymous answers, the timestamps (startdate and datestamp) will stay at default value (1980...)
- if I chose to save timestamp and select "no" to anonymous answers, the timestamps will be saved correctly

I only tried with public access, didn't test with restricted mode

20798: Keyboard + screen reader : access to an hidden element

Fri, 23 Oct 2026 17:02:59 +0200

The close button of the modal didn't have any accessible name (aria-mlabele or content) but it's include in tabulation

20797: Soft mandatory modal A11Y issue with WCAG 1.3.1 — Info and Relationships (Level A)

Fri, 23 Oct 2026 17:02:21 +0200

The links “Continue without answering” and “Answer the question” form a group but are not marked up as a list.

20796: Multi choice with other : Other checkbox not checked with space

Fri, 23 Oct 2026 15:45:42 +0200

If you enter space in other texte : cgheckbox is not checked. Even if the value are not empty

20795: Bootstrap Dropdown question : Inappropriate List Structure

Thu, 22 Oct 2026 18:48:53 +0200

This message “No results matched” is structured as a list (using ul and li tags), which is not appropriate in this context.

20794: Status message not announced

Thu, 22 Oct 2026 18:42:45 +0200

In Bootstrap Dropdown Component – Status Message Not Announced

20793: Not tranlated or tranlatable string in bootstrap_dropdown

Thu, 22 Oct 2026 18:48:37 +0200

The string No results matched "%s" is not translatable.

20792: New survey editor silently drops theme options not defined by fruity_twentythree

Mon, 26 Oct 2026 12:00:14 +0100

The new survey editor validates theme settings against a fixed schema that only lists the option names of fruity_twentythree (themeSettingUpdateJoi). A custom survey theme extending fruity_twentythree can declare extra options in its config.xml, including in optionsOrderReact. The editor shows these options but cannot save them: validation rejects the unknown keys before the request is sent.

The server side already handles this correctly, since it only keeps the options declared in the theme manifest. The client-side whitelist is therefore not needed for safety. It only blocks custom themes.

20791: Decorative element shown for multiple chooice question with other

Mon, 26 Oct 2026 12:55:40 +0100

Currently when check A11Y issues with multiple chooice question with other : we have Success Criterion 3.2.2 On Input https://www.w3.org/TR/WCAG22/#on-input

[Multiple question component with “Other” and exclusivity – Change of context]
When the “Other” checkbox is activated, focus is moved directly to the input field. The label “Other” does not allow users to anticipate this change.
To fix this: Modify the checkbox label to inform users of the associated context (the input field), for example, “Other, please specify below”, and keep focus on the checkbox.

**BUT** it's not the issue here,

When you deactivate JavaScript, check the checkbox and submit : no error but no data saved

The checkbox is a visual decoration ...

20790: More separation for header and navabar

Thu, 22 Oct 2026 12:39:55 +0200

When update theme, there are some part updated a lot

- The header : for favicon, extra css;, extra font extra JS etc ... : we already have custom_header , but think it can be better
- The navbar : for the logo, the title of web site etc ...

For the navbar : if you update only for a fixed logo for example : you set it where the whole tool menu is done.
For the header : just a favicon and you break all futuire updating functionality

20789: Focusable element with aria-hidden

Thu, 22 Oct 2026 09:43:12 +0200

Modal dialog have Close button focusable but

1. With aria-hidden true See 2.4 Fourth Rule of ARIA Use https://www.w3.org/TR/using-aria/#fourth
2. and with keyboard access Success Criterion 2.1.1 Keyboard https://www.w3.org/TR/WCAG22/#keyboard

20788: Soft mandatory Modal : no way to not answer

Fri, 23 Oct 2026 17:03:13 +0200

With a soft mandatory question : on Modal : you cannot select "Continue without answering"

20787: Ranking question : WGAG 1.3.1 Info and Relationships H48

Thu, 22 Oct 2026 09:14:18 +0200

The current 2 rankling question break 1.3.1 Info and Relationships: usage of ul in place of ol

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)

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

Mon, 26 Oct 2026 16:40:18 +0100

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

Fri, 23 Oct 2026 15:57:09 +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