View Issue Details

This issue affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
20572Bug reportsSurvey editingpublic2026-11-01 23:12
ReporterDenisChenu Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status ready for code reviewResolutionreopened 
Product Version7.0.x 
Summary20572: Can not add new element to ranking question in 7.0
Description

In 6.0 : we can add element in ranking quetsion after activation, not tru in 7.0

Steps To Reproduce

Steps to reproduce

Import included survey in 6 or 7 and compare

Expected result

In 7.X : can add element

Actual result

In 7.X : can not add element

TagsNo tags attached.
Attached Files
Bug heat6
Complete LimeSurvey version number (& build)7.0.2
I will donate to the project if issue is resolvedNo
Browsernot relevant
Database type & versionnot relevant
Server OS (if known)not relevant
Webserver software & version (if known)not relevant
PHP Versionnot relevant
Git branch / Pull Request URLhttps://github.com/LimeSurvey/LimeSurvey/pull/5500

Relationships

related to 20571 closedc_schmitz Usage of max_subquestions rankking feature broken 
related to 20573 closedtibor.pacalat Database : ranking question contains unrelated information 
related to 20713 closedc_schmitz Export ranking response as full answer export only code 
related to 20714 closedc_schmitz Ranking questions export is not user-friendly 

Users monitoring this issue

There are no users monitoring this issue.

Activities

tibor.pacalat

tibor.pacalat

2026-06-29 17:18

administrator   ~85106

The difference is that after refactoring, ranking questions have subquestions and not answers any more. This is why this behaviour changed and I don't think this will work as before.

DenisChenu

DenisChenu

2026-06-29 17:20

developer   ~85107

The difference is that after refactoring, ranking questions have subquestions and not answers any more. This is why this behaviour changed and I don't think this will work as before.

It's stille an issue !

Before : you can,
Now : you can't

There are no reason to move to subquestoion

tibor.pacalat

tibor.pacalat

2026-06-30 10:14

administrator   ~85120

We need to fix ranking question type first and then we will come back to this issue.

DenisChenu

DenisChenu

2026-06-30 10:38

developer   ~85125

Then, close this one as a duplicate of https://bugs.limesurvey.org/view.php?id=20573 ?

What do you mean by fix ranking question type ?

c_schmitz

c_schmitz

2026-06-30 10:45

administrator   ~85127

We identified other shortcomings for the new fieldnames on ranking. We are currently working to fix this.

DenisChenu

DenisChenu

2026-06-30 10:58

developer   ~85128

We identified other shortcomings for the new fieldnames on ranking. We are currently working to fix this.

What do you mean? Can we have some explanation?

I see the issue only when working on getQuestionInformation plugin

DenisChenu

DenisChenu

2026-09-21 12:19

developer   ~85883

Last edited: 2026-09-21 12:20

Since now subquestions are not used in the response database, there is no reason to disable adding or remove questions
Maybe need to move to answers (again).

c_schmitz

c_schmitz

2026-09-21 13:16

administrator   ~85886

Yeah, but I would still like to wait with this until we fixed the other issues.
Adding of items in v6 would work but it would also break an active survey, so the comparison it is not exactly fair ;).

DenisChenu

DenisChenu

2026-09-21 15:41

developer   ~85893

Adding of items in v6 would work but it would also break an active survey, so the comparison it is not exactly fair ;).

No, the issue was fixed in v5, maybe in v3; I can find the PR.

Issue History

Date Modified Username Field Change
2026-06-22 16:12 DenisChenu New Issue
2026-06-22 16:12 DenisChenu File Added: survey_archive_CountryList.lsa
2026-06-22 16:12 DenisChenu Relationship added related to 20571
2026-06-22 16:18 DenisChenu Relationship added related to 20573
2026-06-29 17:18 tibor.pacalat Assigned To => tibor.pacalat
2026-06-29 17:18 tibor.pacalat Status new => closed
2026-06-29 17:18 tibor.pacalat Resolution open => won't fix
2026-06-29 17:18 tibor.pacalat Note Added: 85106
2026-06-29 17:18 tibor.pacalat Bug heat 0 => 2
2026-06-29 17:20 DenisChenu Status closed => feedback
2026-06-29 17:20 DenisChenu Resolution won't fix => reopened
2026-06-29 17:20 DenisChenu Note Added: 85107
2026-06-29 17:20 DenisChenu Bug heat 2 => 4
2026-06-30 10:14 tibor.pacalat Note Added: 85120
2026-06-30 10:38 DenisChenu Note Added: 85125
2026-06-30 10:38 DenisChenu Status feedback => assigned
2026-06-30 10:45 c_schmitz Note Added: 85127
2026-06-30 10:45 c_schmitz Bug heat 4 => 6
2026-06-30 10:58 DenisChenu Note Added: 85128
2026-09-21 12:13 DenisChenu Relationship added related to 20713
2026-09-21 12:18 DenisChenu Relationship added related to 20714
2026-09-21 12:19 DenisChenu Note Added: 85883
2026-09-21 12:20 DenisChenu Note Edited: 85883
2026-09-21 13:16 c_schmitz Note Added: 85886
2026-09-21 13:16 c_schmitz Status assigned => acknowledged
2026-09-21 15:41 DenisChenu Note Added: 85893
2026-11-01 23:12 c_schmitz Assigned To tibor.pacalat => c_schmitz
2026-11-01 23:12 c_schmitz Status acknowledged => ready for code review
2026-11-01 23:12 c_schmitz Git branch / Pull Request URL N/A => https://github.com/LimeSurvey/LimeSurvey/pull/5500