| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 20412 | Bug reports | Database design | public | 2026-01-30 13:16 | 2026-01-30 16:22 |
| Reporter | zufolo441 | Assigned To | |||
| Priority | none | Severity | minor | ||
| Status | new | Resolution | open | ||
| Summary | 20412: Subquestion field names in LS 7.0 Beta 1 | ||||
| Description | Hi, maybe there is some problem in field naming. I read in https://www.limesurvey.org/manual/LimeSurvey_7_Fieldname_Refactor that subquestion | ||||
| Steps To Reproduce | Steps to reproduce(Replace this text with detailed step-by-step instructions on how to reproduce the issue) Expected result(Write here what you expected to happen) Actual result(Write here what happened instead) | ||||
| Tags | No tags attached. | ||||
| Bug heat | 6 | ||||
| Complete LimeSurvey version number (& build) | 7.0 beta 1 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | Firefox 147 | ||||
| Database type & version | PostgreSQL 17.7 | ||||
| Server OS (if known) | RHEL 9 | ||||
| Webserver software & version (if known) | |||||
| PHP Version | 8.2 | ||||
 |
Stop. I just understand the logic. it is not the "title" field but "qid" of subquestion. |
|
|
I've just done a test. if I delete a subquestion ad I recreate with same code (title), it doesn't restore data from oldresponses$sid_$timestamp. In my opinion it's a bit problematic. |
 |
If you do same in 6.X and it work: yes, it's problematic. Must be reported separately. (I think we try to use Expression Code for column names in 7.X or 8.X, I don't really understand the interest here.) |
|
|
in v6 it works, because code is part of the field name.... |
|
|
Then it's clearly an issue : no question here ! |
