From: SourceForge.net <no...@so...> - 2009-03-07 19:45:50
|
Bugs item #2669428, was opened at 2009-03-06 12:45 Message generated for change (Comment added) made by kswartz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2669428&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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: kswartz (kswartz) Assigned to: Nobody/Anonymous (nobody) Summary: Copying an existing survey does not copy conditions Initial Comment: I'm working with version 2.0.2 of phpESP, and noticed that if you copy an existing survey, it copies everything BUT the conditions. If this isn't fixed in the latest version, please consider it for the next update. (If this IS fixed in 2.1.2, it will probably speed up my upgrade. Only reason I haven't so far is because I made a lot of changes and fixed some bugs in 2.0.2, and wasn't sure how long it would take to copy the changes over.) ---------------------------------------------------------------------- >Comment By: kswartz (kswartz) Date: 2009-03-07 11:45 Message: Okay, I've set up 2.1.2, and I may have a patch for this coming, but I've discovered a weird quirk that's affecting the SQL. The starting position for all my surveys (in the question table) is 0. However, when I copy a survey, the starting position is 1. Is that intended behavior? Can I always assume that the value of "position" for a question in a copied survey is always one greater than its counterpart in the original survey? ---------------------------------------------------------------------- Comment By: kswartz (kswartz) Date: 2009-03-06 16:01 Message: That's cool - it's not a feature I use very often, which is why it took so long to say anything. Next time I go to do this, I'll add a comment to the request with the SQL necessary to do the copy (which is the hard part). If I have time to actually fix the code, I'll gladly supply a patch. (And yes, I'll upgrade to 2.1.2 first. :) ) ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-03-06 15:40 Message: Hi, sorry, but I don't think it is fixed in 2.1.2 (it was known to me though, and I'm pretty sure I documented it somewhere...) But feel free to make any contribution, be it patches, bug fixes, etc ... Franky ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2669428&group_id=8956 |