Bugs item #1894649, was opened at 2008-02-15 15:50
Message generated for change (Comment added) made by bishopb
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=1894649&group_id=8956
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Admin
Group: None
Status: Closed
Resolution: Later
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Copy an Existing Survey option NOT copying conditions
Initial Comment:
When making a copy of an existing survey in version 2.0.2, the conditions for that survey are NOT being copied (new copy has no conditions).
----------------------------------------------------------------------
>Comment By: bishop (bishopb)
Date: 2008-02-18 12:12
Message:
Logged In: YES
user_id=1982963
Originator: NO
survey_copy() is now just a trivial case of survey_aggregate(), but
survey_aggregate() doesn't do anything with conditions because it is just
an elaboration of the original copy code.
To implement condition copying, a mapping between surveys and their old
and new question ids would have to be established. Then, something like
this:
foreach original survey
get all conditions for that survey
foreach condition
replace survey_id with new survey id
lookup q1_id in map and replace with new q1 id
lookup q2_id in map and replace with new q2 id
insert condition
Most likely, this pseudo code would be put in a loop after the copy survey
question call.
----------------------------------------------------------------------
Comment By: Franky Van Liedekerke (liedekef)
Date: 2008-02-15 18:27
Message:
Logged In: YES
user_id=109671
Originator: NO
This is true and known, but not a bug. For now the copy code is a bit too
sloppy to allow the conditions to be copied as well (since the new
questions have different ID's, it's a bit difficult to correlate the
conditions ...).
If you want this, please open a feature request. Also: new code is in
progress that might just solve this problem.
Franky
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=108956&aid=1894649&group_id=8956
|
