View Issue Details

This issue affects 1 person(s).
 8
IDProjectCategoryView StatusLast Update
17142Bug reportsImport/Exportpublic2026-10-07 23:58
ReporterDenisChenu Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status closedResolutionfixed 
Product Version3.25.12 
Summary17142: Bad order of VV and database column with randomiza
Description

When a survey is tested : randomization happen in database (and then when export VV)

Steps To Reproduce

Import included survey
Activate survey
Launch survey
Move next to see 1st page with question
Close test
Go to your database : check order
Export VV: check order

Additional Information

I realy think we do a complete session when activate.

If we don't do : it can explain bad database (other column, number of column for ranking etc …)

Tested with https://github.com/LimeSurvey/LimeSurvey/pull/1770 fix

TagsNo tags attached.
Attached Files
Bug heat8
Complete LimeSurvey version number (& build)3.25.15
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 URL

Relationships

duplicate of 20606 closedHaythem Response table schema is incorrect when activating a survey after previewing a List (Radio) question with a randomization group 
related to 16867 closedgabrieljenik Randomization happen in survey logic file and in export 
has duplicate 17143 closed Bad order of VV and database column with randomiza 

Users monitoring this issue

There are no users monitoring this issue.

Activities

Issue History

Date Modified Username Field Change
2021-02-28 10:08 DenisChenu New Issue
2021-02-28 10:08 DenisChenu File Added: limesurvey_survey_randomQuestion.lss
2021-02-28 10:08 DenisChenu File Added: Capture d’écran du 2021-02-28 10-03-25.png
2021-02-28 10:08 DenisChenu File Added: Capture d’écran du 2021-02-28 10-04-13.png
2021-02-28 10:08 DenisChenu Relationship added related to 16867
2021-02-28 10:17 DenisChenu Issue cloned: 17143
2021-02-28 10:18 DenisChenu Relationship added related to 17143
2026-10-07 23:57 c_schmitz Assigned To => c_schmitz
2026-10-07 23:57 c_schmitz Status new => closed
2026-10-07 23:57 c_schmitz Resolution open => fixed
2026-10-07 23:57 c_schmitz Relationship added duplicate of 20606
2026-10-07 23:58 c_schmitz Relationship replaced has duplicate 17143
2026-10-07 23:58 c_schmitz Bug heat 0 => 8