View Issue Details

This issue affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
19473Bug reportsQuestion editorpublic2026-09-11 22:06
Reportermarcgold Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status closedResolutionfixed 
Product Version6.4.x 
Summary19473: Cannot save Question after changing duplicate code
Description

Sometime (no idea what causes this) you create a question and it doesn't auto increment the Question number. When this happens, you save the question and it warns you of the duplicate question number.

If you change the number and try and save it still warns of a duplicate number even though it has been updated.

Only solution is to refresh, recreate the question and make sure the number is changed first.

Steps To Reproduce

Steps to reproduce

Create a Question - where there is a duplicate - but this is hard to recreate as it doesn't always happen.
Best way I have found is to Create a Question. Then Copy the Question, The create a new one - the Q numbers should be out of line now - but not always (Sorry)

(Replace this text with detailed step-by-step instructions on how to reproduce the issue)

Expected result

Should be able to change the Duplicate to a Unique and save
(Write here what you expected to happen)

Actual result

(Write here what happened instead)

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)6.4.12+240311
I will donate to the project if issue is resolvedNo
Browserany
Database type & versionMaria 10
Server OS (if known)Ubuntu
Webserver software & version (if known)Nginx
PHP Version8.2
Git branch / Pull Request URL

Users monitoring this issue

There are no users monitoring this issue.

Activities

DenisChenu

DenisChenu

2024-03-13 08:17

developer   ~79784

Create a Question - where there is a duplicate - but this is hard to recreate as it doesn't always happen.

You mean : update to an existing question code, try to save : disable submit and after fix the question code : it's OK; The issue are only when code are same as start ?

c_schmitz

c_schmitz

2026-09-11 22:06

administrator   ~85680

Hello marcgold,
I checked this with the latest version and could not reproduce, so this is most likely fixed for good.
Therefore, I am closing this issue. If you still can reproduce the issue using the latest version, please feel free to re-open the issue.
Thank you!

c_schmitz

Issue History

Date Modified Username Field Change
2024-03-12 20:04 marcgold New Issue
2024-03-13 08:17 DenisChenu Note Added: 79784
2024-03-13 08:17 DenisChenu Bug heat 0 => 2
2026-09-11 22:06 c_schmitz Assigned To => c_schmitz
2026-09-11 22:06 c_schmitz Status new => closed
2026-09-11 22:06 c_schmitz Resolution open => fixed
2026-09-11 22:06 c_schmitz Note Added: 85680
2026-09-11 22:06 c_schmitz Bug heat 2 => 4