LOVD 2.0

Welcome to the LOVD 2.0 bug tracking system. Please note that this bug tracking system is not for LOVD 3.0!

If you have any issues, please read the documentation and Frequently Asked Questions.
Please note that you need to register before you can submit bugs or feature requests.

Information By default, all closed tasks are hidden from view.
Click here to see all tasks.


FS#12 - Selection list value lost on edit of sequence variant

Attached to Project: LOVD 2.0
Opened by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 31 January 2007, 12:13 GMT+1
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 31 January 2007, 13:35 GMT+1
Task Type Bug Report
Category Backend / Core → Variant submission
Status Closed
Assigned To Ivo F.A.C. Fokkema (ifokkema)
Operating System All
Severity Medium
Priority High
Reported Version 2.0-alpha-05
Due in Version 2.0-alpha-06
Due Date 2007-02-09
Percent Complete 100%
Votes 0
Private No


When editing a variant, all variant-related selection list are set at the first item, therefor the previous value is lost.
To reproduce, add the non-standard variant type column to a gene, edit a variant and set the variant type to something different than the default value. Verify in the detailed view that the value is stored. Now, edit the variant again. Notice the selection list value is reset to the default value.
This task depends upon

Closed by  Ivo F.A.C. Fokkema (ifokkema)
Friday, 09 February 2007, 10:55 GMT+1
Reason for closing:  Fixed
Comment by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 31 January 2007, 13:13 GMT+1
This behaviour is also confirmed for patient columns. The current value is not selected. However, it does not occur with multiple selection lists...
Comment by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 31 January 2007, 13:37 GMT+1
Bug found in $_CURRDB->transformSelectValues() that exploded single value selection lists as well, resulting in an array which the form creator could not handle, as it requires a string for single value selection lists.