View Issue Details

This bug affects 2 person(s).
IDProjectCategoryView StatusLast Update
19088Bug reportsMenu systempublic2023-10-23 20:10
Reporterbaxterdmutt Assigned Totibor.pacalat  
Status closedResolutionfixed 
Product Version6.2.x 
Summary19088: Question Array(Text) codes must be unique (but they are)

When adding questions to an Array (Text) after 2 question I can’t save. I keep getting the error “subquestion codes must be unique”. But they are.
All three codes in the Y-Scale are different from each other.
Both codes in the X-Scale are different from each other and I’ve tried both the same and different from the Y-Scale.

Steps To Reproduce

Steps to reproduce

Create a question Array(text) and try to add multiple sub questions to X and Y axis
Even if unique codes, it throws an error.

Expected result

Save question without errors

Actual result

Error “codes must be unique

TagsNo tags attached.
Bug heat16
Complete LimeSurvey version number (& build)6.2.6
I will donate to the project if issue is resolvedNo
Database type & versionMariaDB 11.0.3
Server OS (if known)
Webserver software & version (if known)
PHP VersionTried 7.4 and 8


related to 19108 assignedollehar Error: Subquestion codes should be unique. Cannot save the subquestions even their codes are unique. 
related to 19160 confirmedkfoster Unable to save subquestions 

Users monitoring this issue




2023-09-15 18:31

reporter   ~77079

I've got the same problem with 6.2.6+230904. My Database is MySQL and I'm running the server under PHP 8.1.



2023-09-15 21:56

reporter   ~77080

If you manually change the codes to say X001 (for the X axis) and Y001 (for the Y axis) and make sure to add all the fields to both axis that you will need, and then save it, it’ll be ok. But if you go back and try adding another field after it has been saved, sometimes it works, sometimes it doesn’t



2023-10-05 23:30

manager   ~77532

Last edited: 2023-10-05 23:30

This seems to have been fixed on this PR )for 19108



2023-10-09 15:08

administrator   ~77573

This has already been resolved in the newest version 6.2.11.

Issue History

Date Modified Username Field Change
2023-09-15 18:12 baxterdmutt New Issue
2023-09-15 18:31 fg-marketing-research Note Added: 77079
2023-09-15 18:31 fg-marketing-research Bug heat 0 => 2
2023-09-15 18:32 fg-marketing-research Issue Monitored: fg-marketing-research
2023-09-15 18:32 fg-marketing-research Bug heat 2 => 10
2023-09-15 21:56 baxterdmutt Note Added: 77080
2023-09-15 21:56 baxterdmutt Bug heat 10 => 12
2023-09-18 15:09 gabrieljenik Assigned To => gabrieljenik
2023-09-18 15:09 gabrieljenik Status new => assigned
2023-09-22 15:09 gabrieljenik Relationship added related to 19108
2023-10-05 23:30 gabrieljenik Assigned To gabrieljenik => tibor.pacalat
2023-10-05 23:30 gabrieljenik Status assigned => ready for testing
2023-10-05 23:30 gabrieljenik Note Added: 77532
2023-10-05 23:30 gabrieljenik Bug heat 12 => 14
2023-10-05 23:30 gabrieljenik Note Edited: 77532
2023-10-09 15:08 tibor.pacalat Status ready for testing => closed
2023-10-09 15:08 tibor.pacalat Resolution open => fixed
2023-10-09 15:08 tibor.pacalat Note Added: 77573
2023-10-09 15:08 tibor.pacalat Bug heat 14 => 16
2023-10-23 20:10 mfavetti Relationship added related to 19160