View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
04534Bug reportsOtherpublic2010-08-16 12:042010-10-13 16:22
Reportermdekker Assigned Tomdekker  
PriorityhighSeveritypartial_block 
Status closedResolutionfixed 
Product Version1.90+ 
Fixed in Version1.90+ 
Summary04534: Sometimes multiple options questions get the other field while they shouldn't
Description

There is an error in the createfieldmap function that causes certain surveys to have other fields for type M & P questions. The reason is that alsoother variable is only set to Y when needed, but never reset. Once we have a Y value all following questions get the other option.

Additional Information

As this function is used to create the database, there are also extra fields in the database. As far as I have quickly checked qanda.php checks for the other fields itself and doesn't depend on the fieldmap so for survey taking there is no error.

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)9061
I will donate to the project if issue is resolved
Browser
Database type & versiondna
Server OS (if known)dna
Webserver software & version (if known)dna
PHP Versiondna

Users monitoring this issue

There are no users monitoring this issue.

Activities

mdekker

mdekker

2010-08-16 12:06

reporter   ~12633

It can be fixed easily by updating the fieldmap function but some people can be left with a database that has some extra fields. Not sure what will happen there as sometimes we read the fields in the table and sometimes we use a fieldmap.
c_schmitz

c_schmitz

2010-08-16 22:41

administrator   ~12638

Menno, afaik we always use the fieldmap - I would not know any place where the actual fields are used as orientation. Just update the fieldmap function so these obsolete fields are not created anymore.
mdekker

mdekker

2010-08-17 08:39

reporter   ~12641

Last edited: 2010-08-17 08:42

I know that in SPSS / R export I go through all the database fields and try to match them against a fieldmap field. And as a lot of older functions are copy/paste/modify I think there might be other places where this is done. Still impact should be minor as it was only present for a short time i think and only under certain conditions.

I will see if i can find problems in code and fix them as i find them or mark them here. I will commit the fieldmap fix now so it can go in a plus version.

Edit: createfieldmap was fixed in svn 9065
c_schmitz

c_schmitz

2010-08-17 09:20

administrator   ~12642

tse, tse, you should never rely on the table, always on the getfieldmap function ;)
mdekker

mdekker

2010-10-08 11:05

reporter   ~13042

The fieldmap function was updated a while ago and I am not aware of any resulting errors so the bug can be closed.
c_schmitz

c_schmitz

2010-10-13 16:22

administrator   ~13129

Released in latest Plus version

Issue History

Date Modified Username Field Change
2010-08-16 12:04 mdekker New Issue
2010-08-16 12:05 mdekker Assigned To => mdekker
2010-08-16 12:05 mdekker Status new => assigned
2010-08-16 12:06 mdekker Note Added: 12633
2010-08-16 12:06 mdekker Assigned To mdekker => c_schmitz
2010-08-16 12:06 mdekker Status assigned => feedback
2010-08-16 22:41 c_schmitz Note Added: 12638
2010-08-16 22:41 c_schmitz Assigned To c_schmitz => mdekker
2010-08-16 22:41 c_schmitz Status feedback => assigned
2010-08-17 08:39 mdekker Note Added: 12641
2010-08-17 08:42 mdekker Note Edited: 12641
2010-08-17 09:20 c_schmitz Note Added: 12642
2010-10-08 11:05 mdekker Note Added: 13042
2010-10-08 11:05 mdekker Status assigned => resolved
2010-10-08 11:05 mdekker Fixed in Version => 1.90+
2010-10-08 11:05 mdekker Resolution open => fixed
2010-10-13 16:22 c_schmitz Note Added: 13129
2010-10-13 16:22 c_schmitz Status resolved => closed