A Key for Migrating Key Expressions from 2.x to 3.x

Plus d'informations
il y a 4 jours 5 heures #168865 par duvemyster
duvemyster a créé le sujet : A Key for Migrating Key Expressions from 2.x to 3.x
Has a key already been development somewhere outlining key expressions what work in 2.x that would need to be changed in a migration to 3.x, and how they would need to be change?

For example, in 2.x in the template editor a survey name is {SURVEYNAME} but in the 3.x theme editor it is {{ aSurveyInfo.name }}. Which of the depreciated keywords have a similar method like this by which they can be referenced in 3.x?

Has something along those lines already been developed? It sure would be helpful!

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 3 jours 12 heures - il y a 3 jours 12 heures #168922 par tpartner
tpartner a répondu au sujet : A Key for Migrating Key Expressions from 2.x to 3.x
These are two different things.

{{ aSurveyInfo.name }} is Twig variable.
To see all available items in the aSurveyInfo array, add this to the Twig file:

{{ dump(aSurveyInfo) }}

{SURVEYNAME} is an Expression Manager variable.
Denis has implemented a fix so we can also access those in the Twig files - github.com/LimeSurvey/LimeSurvey/pull/1025 .
So, to use that, you would place something like this in the Twig file:

{{ processString(aSurveyInfo.surveyls_title) }}
{{ processString('{SURVEYLANGUAGE}') }}
{{ processString('{strip_tags(TOKEN:ATTRIBUTE_1)}') }}

Cheers,
Tony Partner
Solutions, code and workarounds presented in these forums are given without any warranty, implied or otherwise.
Dernière édition: il y a 3 jours 12 heures par tpartner.
Les utilisateur(s) suivant ont remercié: duvemyster

Connexion ou Créer un compte 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!