Question Code updates

Plus d'informations
il y a 3 ans 8 mois #105957 par LSCitizen
LSCitizen a créé le sujet : Question Code updates
I am currenty using LimeSurvey: Version 2.05+ Build 140226.

I have imported a survey from an instance of LimeSurvey using Version 1.92+ Build 120620.
When I imported the survey, all of the question codes that uses an underscore (_) were changed.

Is there a way to prevent this from happening? I have attached a screenshot.
Pièces jointes :

Connexion pour participer à la conversation.

Plus d'informations
il y a 3 ans 8 mois #105964 par c_schmitz
c_schmitz a répondu au sujet : Question Code updates
No, I am sorry but you cannot prevent this from happening.

Best regards

Carsten Schmitz
LimeSurvey project leader

Connexion pour participer à la conversation.

Plus d'informations
il y a 3 ans 8 mois #106137 par LSCitizen
LSCitizen a répondu au sujet : Question Code updates
Why has this changed?

Connexion pour participer à la conversation.

Plus d'informations
il y a 3 ans 8 mois #106167 par tpartner
tpartner a répondu au sujet : Question Code updates
Underscores are no longer allowed in question/sub-question codes because they cause problems in Expression Manager because it uses underscores to connect questions subquestion and answers in variable names.


.

Cheers,
Tony Partner
Solutions, code and workarounds presented in these forums are given without any warranty, implied or otherwise.

Connexion pour participer à la conversation.

Plus d'informations
il y a 3 ans 8 mois #106214 par rvenkat
rvenkat a répondu au sujet : Question Code updates
Does this mean existing surveys with underscores in question codes have to be changed.
If so, that's a bit of pain when there are conditions.


RV

Connexion pour participer à la conversation.

Plus d'informations
il y a 3 ans 8 mois #106319 par TMSWhite
TMSWhite a répondu au sujet : Question Code updates
Just to be clear, Expression Manager doesn't have any trouble with underscores -- it has supported them just fine since 1.92.

Rather, it appears that the team was concerned that users could accidentally generate duplicate variable names (since questions types with sub-questions have variable names that are auto-created as a combination of the question code plus and underscore plus the sub-question code; and this could conflict with explicitly created variable names for other types of questions if underscores are allowed). The Show Survey Logic File has explicitly shown cases where questions contain duplicated question codes (by surrounding them with a pink box, and including tool-tips that refer you to the duplicate question) since 1.92, but it appears that the team did not feel that was an adequate solution.

The newer versions of 2.05+ do attempt to remove underscores from variables during upgrade, but the team could use some help from the community to improve the robustness of that process. If you have surveys with underscores in the variable names, you should explicitly check the accuracy of array_filter, array_filter exclude, and other non-question text blocks that use those variables, since the upgrade process does not currently address those aspects of the survey. You should also check that the removal of the underscores during upgrade did not cause other variable names to now clash. The Show Logic File will help you identify and fix such issues.

Connexion pour participer à la conversation.

Commencez dès maintenant !

Créez simplement un compte et commencez à utiliser LimeSurvey dès aujourd'hui.

Inscrivez-vous maintenant

Inscrivez-vous à notre Newsletter!