| Anonymous | Login | 2010-07-31 22:58 CEST | |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |
| 04115 | Bug reports v1.x | Survey Design | public | 2010-02-09 10:23 | 2010-02-18 15:20 | |
| Reporter | apps | |||||
| Assigned To | lemeur | |||||
| Priority | normal | Severity | crash | Reproducibility | always | |
| Status | closed | Resolution | won't fix | |||
| Platform | OS | OS Version | ||||
| Product Version | 1.87 | |||||
| Target Version | Fixed in Version | |||||
| Summary | 04115: Survey Import does not recreate token's custom field | |||||
| Description | Reproduce: 1) make a survey 2) create a custom field "flag" in token management 3) create a question 4) add a condition binding to flag's value, e.g. IF "flag" [from token table] = 1 5) export the survey in .csv 6) import the survey What gone wrong: the new survey hasn't a token table (it's ok for me) but the conditions are still there, they are referring to an inexistant token table. you must create it. When creating the token table, the survey is not aware he needs an extra field. Still, the conditions refers to an inexistant field. You must create it/them | |||||
| Additional Information | What should happen? The token table, when initialized, should recreate the custom fields needed for the survey logic, in an automatic way! The user could get fooled by the fact that no there are no signs that the survey will require those fields. Aslo, that the fields show match their original name to be fully functionaly. Also, at survey import, there is clearly the need of a more compelling message that a token table is mandatory this time. IF the previous hint get implemented, when token table get created, the fields are imported back and the survey will be fine. | |||||
| Tags | No tags attached. | |||||
| LimeSurvey build number | 8278 | |||||
| Browser | ff3 | |||||
| Database & DB-Version | mysql | |||||
| Operating System (Server) | debian | |||||
| Webserver | apache | |||||
| PHP Version | 5.1.6 | |||||
| Attached Files | ||||||
 Relationships |
|
 Relationships |
|
Notes |
|
 (11094)ElMatador69 (administrator) 2010-02-14 22:37 |
On my knowledge thats no bug, that's a known limitation of the current version. @ Lemeur: Am I right? |
 (11099)lemeur (administrator) 2010-02-15 09:49 |
Yes, this is a limitation of current version and it's not easy to fix since the survey structure that contains the conditions is independent from the token CSV file. Note also that the conditions only refers to the internal token attribtue name (that is to say ATTRIBUTE_1 or ATTRIBUTE_2, ..., and not the label attached to it "flag"). All we can do so far is to raise a warning at import time if we find token placeholders in conditions for a survey, in order to remind the survey admin that a token table with at least X token attribtues must be created, but that's not much. |
 (11100)apps (reporter) 2010-02-15 12:05 |
Blinking note: I'm using the export/inport method because there is no "clone survey" feat! Seriously. Take a look at this idea http://ideas.limesurvey.org/ideatorrent/idea/100/ [^] A copy survey feat, executed inside the admin zone, will not pass throug a csv format, so it won't hit the csv format specs. To duplicate the custom fields will be trivial from there. |
|
(11104) apps (reporter) 2010-02-15 16:54 |
anyway, thx to Lemeur for pointing out the importante of the attribute code over the label. |
|
(11129) lemeur (administrator) 2010-02-18 15:20 |
Closing this ticket as this is no bug and since the feature request is already in the idea tracker. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-02-09 10:23 | apps | New Issue | |
| 2010-02-09 10:23 | apps | Status | new => assigned |
| 2010-02-09 10:23 | apps | Assigned To | => ElMatador69 |
| 2010-02-09 10:23 | apps | LimeSurvey build number | => 8278 |
| 2010-02-09 10:23 | apps | Browser | => ff3 |
| 2010-02-09 10:23 | apps | Database & DB-Version | => mysql |
| 2010-02-09 10:23 | apps | Operating System (Server) | => debian |
| 2010-02-09 10:23 | apps | Webserver | => apache |
| 2010-02-09 10:23 | apps | PHP Version | => 5.1.6 |
| 2010-02-14 22:37 | ElMatador69 | Note Added: 11094 | |
| 2010-02-14 22:37 | ElMatador69 | Assigned To | ElMatador69 => lemeur |
| 2010-02-15 09:49 | lemeur | Note Added: 11099 | |
| 2010-02-15 12:05 | apps | Note Added: 11100 | |
| 2010-02-15 16:54 | apps | Note Added: 11104 | |
| 2010-02-18 15:20 | lemeur | Note Added: 11129 | |
| 2010-02-18 15:20 | lemeur | Status | assigned => closed |
| 2010-02-18 15:20 | lemeur | Resolution | open => won't fix |
|
Issue History |
| Copyright © 2000 - 2010 MantisBT Group |
 |