View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 8
IDProjectCategoryView StatusDate SubmittedLast Update
16129Bug reportsSurvey takingpublic2020-04-12 15:312020-05-12 15:01
Reporterong Assigned Topstelling  
PriorityhighSeveritypartial_block 
Status closedResolutionfixed 
Product Version4.1.16 
Summary16129: Array question, '(Sub-)question width' not saved
Description

Hi

in an array question (type F) the "(Sub-)question width" seems not to be saved. I enter a value, but after saving it's gone.

Steps To Reproduce

Create array (type f) question,
add subquestions (with looong text)

TagsNo tags attached.
Attached Files
no_save_sub_q_width.gif (905,315 bytes)
Bug heat8
Complete LimeSurvey version number (& build)4.1.16+200407
I will donate to the project if issue is resolvedNo
Browservivaldi, chromium
Database type & versionmysql 8.0.18
Server OS (if known)debian
Webserver software & version (if known)apache2
PHP Version7.3

Users monitoring this issue

There are no users monitoring this issue.

Activities

cdorin

cdorin

2020-05-08 23:39

reporter   ~57641

Hello @ong, could you please update and test with the latest master version?
ong

ong

2020-05-09 09:29

reporter   ~57642

Last edited: 2020-05-12 15:00

HI cdorin,
I wanted to wait until monday for the new release, in which one there should be another (major) bug solved that I reported. Is that ok, of should I try already now?
DenisChenu

DenisChenu

2020-05-09 10:38

developer   ~57643

Last edited: 2020-05-12 15:00

Some other question attribute are not saved and it's fixed in current release …

Then : maybe …

and it's quick to upgrade minor release …
ong

ong

2020-05-09 11:13

reporter   ~57644

Last edited: 2020-05-12 15:00

Hi,

ok, updated (to 4.2.2+200504), but the problem that occurs now was reported by me before (https://bugs.limesurvey.org/view.php?id=16076): Saving is not possible anymore :-( so I guess, at this time I am not even able to test if it works.
See attaches animated image.

no_save.gif (1,305,757 bytes)
pstelling

pstelling

2020-05-12 15:01

developer   ~57701

This reported bug seems to be solved in newest master branch.

Issue History

Date Modified Username Field Change
2020-04-12 15:31 ong New Issue
2020-04-12 15:31 ong File Added: no_save_sub_q_width.gif
2020-04-16 18:45 cdorin Priority none => high
2020-04-16 18:45 cdorin Severity minor => partial_block
2020-04-16 18:45 cdorin Status new => confirmed
2020-04-16 18:45 cdorin Description Updated
2020-04-16 18:45 cdorin Steps to Reproduce Updated
2020-04-16 18:45 cdorin Zoho Sprints => |Yes|
2020-04-16 18:45 swendrich Zoho Sprints ID => 14469000000045001
2020-05-08 23:39 cdorin Note Added: 57641
2020-05-09 09:29 ong Note Added: 57642
2020-05-09 10:38 DenisChenu Note Added: 57643
2020-05-09 11:13 ong Note Added: 57644
2020-05-09 11:13 ong File Added: no_save.gif
2020-05-12 15:00 swendrich Zoho Sprints Yes => |Yes|
2020-05-12 15:00 swendrich Status confirmed => resolved
2020-05-12 15:01 pstelling Assigned To => pstelling
2020-05-12 15:01 pstelling Status resolved => closed
2020-05-12 15:01 pstelling Resolution open => fixed
2020-05-12 15:01 pstelling Note Added: 57701