respondage_vanilla/config.xml

498 lines
38 KiB
XML
Raw Permalink Normal View History

<?xml version="1.0" encoding="UTF-8"?>
<!--
(¯`·._.·(¯`·._.· Vanilla Theme Manifest ·._.·´¯)·._.·´¯)
Base configuration for Vanilla Theme.
The content of this file is imported into DB when you install the template.
Line endings: ALL text files in this theme (including this config.xml) use
LF (Unix) line endings only - no CRLF, no lone CR. This is enforced by
.gitattributes (* text=auto eol=lf). Keep it that way so diffs stay
readable; do not re-save files with CRLF line endings.
-->
<config>
<!-- Those metadata are displayed in the theme configuration page. -->
<metadata>
<name>respondage_vanilla</name>
<title>Respondage Vanilla</title>
<type>theme</type>
<creationDate>2024-04-19 12:03</creationDate>
<author>admin</author>
<authorEmail>tammo.terhark@respondage.nl</authorEmail>
<authorUrl>http://www.respondage.nl</authorUrl>
<copyright>Copyright (C) 2026 Respondage. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later</license>
<version>3.1.0</version>
<apiVersion>3</apiVersion>
<description><![CDATA[<strong>Respondage Theme based on core theme Vanilla</strong><br>A clean and simple base that was used by a certain theme developer to create a really clean theme.]]></description>
<lastUpdate>2026-11-16 19:13:27</lastUpdate>
<extends>vanilla</extends>
</metadata>
<compatibility>
<version>6.0</version>
<version>7.0</version>
</compatibility>
<!--
Here the list of the css/js files to add to the template package.
About packages in Yii: http://www.yiiframework.com/doc/api/1.1/CClientScript#packages-detail
NOTE: The "add" tag also count as a "replace" tag.
Eg: You can't just "add" a file in the extended theme with the same name as a file here. It will always "replace" it. You must use a diffrent file name.
Eg: Vanilla manifest already has "<add>css/theme.css</add>". So if you use "<add>css/theme.css</add>" in an extended theme, it will replace the vanilla css/theme.css
NOTE: If an extended theme, if you don't change a file that is defined here, you don't need to add it again.
Eg: css/ajaxify.css is already added in vanilla. Nor fruity nor bootswatch modify it, so ne need to add / replace it in fruity or bootswatch.
Even if no mention at all about "css/ajaxify.css" is theme extending vanilla, it will still be added because it's added here
NOTE: To easy test changes in config file, you can force the use of the XML file rather than DB. To do so, turn debug mode on, and in config.php config array, on bottom of debug mode, add:
'force_xmlsettings_for_survey_rendering' => true,
Then, you will not need anymore to reset your theme each time you change the config file.
But, once turning the setting off, You will still must reset the theme to the changes are pushed to DB
-->
<files>
<css>
<add>css/base.css</add>
<add>css/theme.css</add>
<add>css/noTablesOnMobile.css</add>
<add>css/plain.css</add>
<add>css/custom.css</add>
</css>
<js>
<add>scripts/theme.js</add>
<add>scripts/custom.js</add>
</js>
<print_css>
<add>css/print_theme.css</add>
</print_css>
</files>
<!-- You can add here any option you want. It will be available in twig file via aSurveyInfo.options.youroptionname -->
<!--
HOUSE-STYLE CONVENTION:
- Options in sections marked "HOUSE-STYLE" are house-style specific:
colors, fonts and the sizes/colors/weights of those fonts, plus
logo on/off + file, logo top margin and background image/color.
- House-style values are ONLY set per client in variants/<client>.json
(processed by variants/build.php into the variant's config.xml).
Never hardcode them in views/, sass/, css/ or scripts/: those files
are shared with all variants.
- Unmarked options are functional/structural (default of the mother
theme, same for all variants). A variant may still override them via
the json; build.php checks that the key exists.
-->
<options>
<hideprivacyinfo type="buttons" category="Simple options" width="4" title="Hide privacy info" options="on|off" optionlabels="Yes|No">off</hideprivacyinfo>
<container type="buttons" category="Simple options" width="4" title="Survey container" options="on|off" optionlabels="Yes|No">on</container>
<showpopups type="buttons" category="Simple options" width="4" title="Show popups" options="1|0|-1" optionlabels="Popup|On page|No">1</showpopups>
<showclearall type="buttons" category="Simple options" width="4" title="Show Clear All button" options="on|off" optionlabels="Yes|No">off</showclearall>
<fixnumauto type="buttons" category="Simple options" width="4" title="Fix automatically numeric value" options="enable|partial|disable" optionlabels="Yes|For expression|No">enable</fixnumauto>
<!-- Images
HOUSE-STYLE: logos (on/off + file), logotopmargin, background image
and bodybackgroundcolor are set per variant via variants/<client>.json -->
<!-- Images -->
<brandlogo type="buttons" category="Images" width="2" title="Display logo on the left of the header" options="on|off" optionlabels="Yes|No">on</brandlogo>
<brandlogofile type="imagefile" category="Images" width="7" title="Logo file (left)" parent="brandlogo">./files/logo.png</brandlogofile>
<centerlogo type="buttons" category="Images" width="2" title="Display logo in the center of the header" options="on|off" optionlabels="Yes|No">off</centerlogo>
<centerlogofile type="imagefile" category="Images" width="7" title="Logo file (center)" parent="centerlogo">./files/logo.png</centerlogofile>
<rightlogo type="buttons" category="Images" width="2" title="Display logo on the right of the header" options="on|off" optionlabels="Yes|No">off</rightlogo>
<rightlogofile type="imagefile" category="Images" width="7" title="Logo file (right)" parent="rightlogo">./files/logo2.png</rightlogofile>
<logotopmargin type="duration" category="Images" width="3" title="Distance from the logo to the top of the screen (use 0px to align a logo exactly with the very top)">15px</logotopmargin>
<backgroundimage type="buttons" category="Images" width="4" title="Background image (behind body of page)" options="on|off" optionlabels="Yes|No">on</backgroundimage>
<backgroundimagefixed type="buttons" category="Images" width="4" title="Background image fixed or scroll" options="fixed|scroll" optionlabels="Fixed|Scroll">scroll</backgroundimagefixed>
<backgroundimagedisplay type="buttons" category="Images" width="4" title="Background image display" options="tile|cover" optionlabels="Tile|Cover">tile</backgroundimagedisplay>
<backgroundimagefile type="imagefile" category="Images" width="12" title="Background image file" parent="backgroundimage">./files/tiledtexture.png</backgroundimagefile>
<bodybackgroundcolor type="colorpicker" category="Images" width="8" title="Overall background color (when there is no picture in the background)" options="on|off" optionlabels="Yes|No">#dddddd</bodybackgroundcolor>
<!-- Questions
HOUSE-STYLE: the colorpicker options in this section (question
title/background/help/border/checkbox colors) are house-style colors.
NOT house-style (structural, same for all variants): questionborder,
questionborderstyle, the borderradius values, questiondropdown and
questionhelptextposition. -->
<!-- Questions -->
<questiontitlebackgroundcolor type="colorpicker" category="Questions" width="6" title="Question title background color" options="on|off" optionlabels="Yes|No">#5e1c64</questiontitlebackgroundcolor>
<questiontitlefontcolor type="colorpicker" category="Questions" width="6" title="Question title font color" options="on|off" optionlabels="Yes|No">#ffffff</questiontitlefontcolor>
<questionbackgroundcolor type="colorpicker" category="Questions" width="6" title="Question background color (not title)" options="on|off" optionlabels="Yes|No">#ffffff</questionbackgroundcolor>
<questionhelpbackgroundcolor type="colorpicker" category="Questions" width="6" title="Question helpbackground color" options="on|off" optionlabels="Yes|No">#fff3cd</questionhelpbackgroundcolor>
<questionborder type="buttons" category="Questions" width="6" title="Question border" options="box|top|none" optionlabels="Box around|Top and bottom|None">box</questionborder>
<questionborderstyle type="buttons" category="Questions" width="6" title="Question border line style" options="solid|dotted|dashed" optionlabels="Solid|Dotted|Dashed">solid</questionborderstyle>
<questionbordercolor type="colorpicker" category="Questions" width="12" title="Question border color" options="on|off" optionlabels="Yes|No">#cccccc</questionbordercolor>
<questionborderradiusTL type="duration" category="Questions" width="3" title="Border radius top left">5px</questionborderradiusTL>
<questionborderradiusTR type="duration" category="Questions" width="3" title="Border radius top right">5px</questionborderradiusTR>
<questionborderradiusBL type="duration" category="Questions" width="3" title="Border radius bottom left">5px</questionborderradiusBL>
<questionborderradiusBR type="duration" category="Questions" width="3" title="Border radius bottom right">5px</questionborderradiusBR>
<questiondropdown type="buttons" category="Questions" width="6" title="Question dropdown shadow" options="on|hover|off" optionlabels="Always|On hover only|None">hover</questiondropdown>
<questionhelptextposition type="buttons" category="Questions" width="6" title="Question help text position" options="top|bottom" optionlabels="Top|Bottom">top</questionhelptextposition>
<checkboxcolor type="colorpicker" category="Questions" width="6" title="Checkbox/radiobutton color (when checked)" options="on|off" optionlabels="Yes|No">#ff005f</checkboxcolor>
<!-- Progress -->
<progressbarposition type="buttons" category="Progress" width="6" title="Position of the progress bar" options="under|in" optionlabels="Under header|In header">under</progressbarposition>
<!-- Various colors
HOUSE-STYLE: ALL colorpickers in this section (header, navbar menu,
primary, font, slider, progressbar, privacy) are house-style colors
and are set per variant via variants/<client>.json -->
<!-- Various colors -->
<headerbackgroundcolor type="colorpicker" category="Colors" width="12" title="Header background color" options="on|off" optionlabels="Yes|No">#eeeeee</headerbackgroundcolor>
<navbarfontcolor type="colorpicker" category="Colors" width="12" title="Menu item text color in the top bar (should contrast with the header background color)" options="on|off" optionlabels="Yes|No">#444444</navbarfontcolor>
<primarycolor type="colorpicker" category="Colors" width="12" title="Primary color (for buttons)" options="on|off" optionlabels="Yes|No">#5e1c64</primarycolor>
<fontcolor type="colorpicker" category="Colors" width="12" title="Base font color" options="on|off" optionlabels="Yes|No">#444444</fontcolor>
<sliderhandlecolor type="colorpicker" category="Colors" width="12" title="Slider handle color" options="on|off" optionlabels="Yes|No">#5e1c64</sliderhandlecolor>
<progressbarbackgroundcolor type="colorpicker" category="Colors" width="12" title="Progress bar background color" options="on|off" optionlabels="Yes|No">#eeeeee</progressbarbackgroundcolor>
<progressbarcolor type="colorpicker" category="Colors" width="12" title="Progress bar color" options="on|off" optionlabels="Yes|No">#5e1c64</progressbarcolor>
<progressbarfontcolor type="colorpicker" category="Colors" width="12" title="Progress bar font color" options="on|off" optionlabels="Yes|No">#ffffff</progressbarfontcolor>
<privacybackgroundcolor type="colorpicker" category="Colors" width="12" title="Privacy background color" options="on|off" optionlabels="Yes|No">lightyellow</privacybackgroundcolor>
<!-- fonts
HOUSE-STYLE: the whole Fonts section (font choice, fontsize and all
font sizes/weights) is house-style specific.
PLACING A CUSTOM FONT - instructions:
1. Put the font file (e.g. .woff2) in the files/fonts/ folder of
the variant (or of this mother theme if all variants should be
able to pick the font).
2. Create a css file in the variant, e.g. css/variant.css, with the
@font-face and the body class (the selected font is applied as
class font-<value> on <body>):
@font-face {
font-family: 'My Custom Font';
src: url('../files/fonts/my-custom-font.woff2') format('woff2');
}
body.font-my_custom_font {
font-family: 'My Custom Font', Arial, sans-serif;
}
('../files/...' works because the asset manager copies the whole
theme dir; in css of the mother theme likewise: ../files/fonts/...)
3. Add to variants/<client>.json:
"files_add": { "css": ["css/variant.css"], "js": [] },
"fontOptions": [ { "value": "my_custom_font",
"label": "My Custom Font" } ]
build.php appends the css to the <files> list and the font to the
"Custom (this theme)" optgroup below. data-font-package stays
"websafe": LimeSurvey only knows core font packages
(application/config/fonts.php); the actual font is loaded via
the variant's own css.
4. Run: php variants/build.php <client> and upload/reset the theme.
See also README.md ("Custom fonts per variant"). -->
<!-- fonts -->
<!-- When adding new items, please keep fonts ordered alphabetically -->
<font type="dropdown" category="Fonts" width="4" title="Fonts" parent="font">opensans
<dropdownoptions>
<!-- Custom fonts of a variant are appended to the optgroup below by variants/build.php ("fontOptions" in the variant json) -->
<optgroup label="Custom (this theme)">
</optgroup>
<optgroup label="User browser">
<option class="font-arial " value="arial" data-font-package="websafe">Arial</option>
<option class="font-arial_black " value="arial_black" data-font-package="websafe">Arial Black</option>
<option class="font-comic_sans " value="comic_sans" data-font-package="websafe">Comic Sans</option>
<option class="font-courier " value="courier" data-font-package="websafe">Courier New</option>
<option class="font-georgia " value="georgia" data-font-package="websafe">Georgia</option>
<option class="font-impact " value="impact" data-font-package="websafe">Impact</option>
<option class="font-lucida_console " value="lucida_console" data-font-package="websafe">Lucida Console</option>
<option class="font-lucida_sans " value="lucida_sans" data-font-package="websafe">Lucida Sans</option>
<option class="font-palatino " value="palatino" data-font-package="websafe">Palatino Linotype</option>
<option class="font-times_new_roman " value="times_new_roman" data-font-package="websafe">Times New Roman</option>
<option class="font-trebuchet " value="trebuchet" data-font-package="websafe">Trebuchet</option>
</optgroup>
</dropdownoptions>
</font>
<fontsize type="buttons" category="Fonts" width="12" title="Base font size" options="14px|16px|18px|20px" optionlabels="Small (14px)|Normal (16px)|Large (18px)|Extra large (20 px)">16px</fontsize>
<questiontitlefontsize type="buttons" category="Fonts" width="6" title="Question title font size" options="1.0rem|1.2rem|1.5rem|2.0rem|20px|24px" optionlabels="Same as Base Font Size(BFS)|1.2 BFS|1.5 BFS|2.0 BFS|20px|24px">1.2rem</questiontitlefontsize>
<questiontitlefontweight type="buttons" category="Fonts" width="6" title="Question title font weight" options="400|700" optionlabels="Normal|Bold">700</questiontitlefontweight>
<grouptitlefontsize type="buttons" category="Fonts" width="6" title="Group title font size" options="1.0rem|1.2rem|1.5rem|2.0rem|20px|24px" optionlabels="Same as Base Font Size(BFS)|1.2 BFS|1.5 BFS|2.0 BFS|20px|24px">2.0rem</grouptitlefontsize>
<grouptitlefontweight type="buttons" category="Fonts" width="6" title="Group title font weight" options="400|700" optionlabels="Normal|Bold">700</grouptitlefontweight>
<groupdescriptionfontsize type="buttons" category="Fonts" width="6" title="Group description font size" options="1.0rem|1.2rem|1.5rem|2.0rem|20px|24px" optionlabels="Same as Base Font Size(BFS)|1.2 BFS|1.5 BFS|2.0 BFS|20px|24px">1.2rem</groupdescriptionfontsize>
<groupdescriptionfontweight type="buttons" category="Fonts" width="6" title="Group description font weight" options="400|700" optionlabels="Normal|Bold">400</groupdescriptionfontweight>
</options>
<!-- Here datas about how LimeSurvey should load the theme -->
<engine>
<!-- core: use core options view file, custom: use customized options.twig view file -->
<optionspage>core</optionspage>
<!-- If empty, bootstrap css/js files will not be loaded. In the future, we may have more engines, like foundation -->
<cssframework>
<name>bootstrap</name>
</cssframework>
<!-- Path of the views files (can be different than views -->
<viewdirectory>views</viewdirectory>
<!-- Asset manager will copy the whole theme directory to tmp. So it's possible to refer any file in the files directory in CSS via relative path (e.g: '../files/foo.jpg') -->
<filesdirectory>files</filesdirectory>
<!-- Here, you can publish packages set as third party extensions in application/config/vendor or application/config/package -->
<!-- If bootstrap is registered as a css framework, it will be loaded first -->
<packages>
<add>pjax</add>
<add>moment</add>
<add>font-noto</add>
</packages>
<!--
List of pages/files for tempalte editor
When a user select a page, the related files will be offer in the editable files
-->
<template_editor>
<screens>
<question>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Question')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="content">./subviews/content/main.twig</file>
<file type="view" role="subview">./subviews/messages/justsaved.twig</file>
<file type="view" role="subview">./subviews/survey/group.twig</file>
<file type="view" role="subview">./subviews/survey/group_subviews/group_container.twig</file>
<file type="view" role="subview">./subviews/survey/group_subviews/group_desc.twig</file>
<file type="view" role="subview">./subviews/survey/group_subviews/group_name.twig</file>
<file type="view" role="subview">./subviews/survey/question.twig</file>
<file type="view" role="subview">./subviews/survey/question_container.twig</file>
<file type="view" role="subview">./subviews/survey/question_subviews/question_text_container.twig</file>
<file type="view" role="subview">./subviews/survey/question_subviews/question_text_content.twig</file>
<file type="view" role="subview">./subviews/survey/question_subviews/answers.twig</file>
<file type="view" role="subview">./subviews/survey/question_subviews/survey_question_help.twig</file>
<file type="view" role="subview">./subviews/survey/question_subviews/valid_message_and_help.twig</file>
<file type="css">./css/theme.css</file>
<file type="js">./scripts/theme.js</file>
<file type="css">./css/custom.css</file>
<file type="js">./scripts/custom.js</file>
</question>
<surveylist>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Survey list')}} ]]></screen_title>
<file type="view" role="layout">layout_survey_list.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="subview">./subviews/content/mainrow.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="subview">./subviews/navigation/language_changer_form.twig</file>
<file type="css">./css/theme.css</file>
<file type="js">./scripts/theme.js</file>
<file type="css">./css/custom.css</file>
<file type="js">./scripts/custom.js</file>
</surveylist>
<welcome>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Welcome')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="subview">./subviews/content/mainrow.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="content">./subviews/content/firstpage.twig</file>
<file type="view" role="subview">./subviews/header/head.twig</file>
<file type="view" role="subview">./subviews/header/custom_header.twig</file>
<file type="view" role="subview">./subviews/header/nav_bar.twig</file>
<file type="view" role="subview">./subviews/header/progress_bar.twig</file>
<file type="view" role="subview">./subviews/messages/welcome.twig</file>
<file type="view" role="subview">./subviews/messages/warnings.twig</file>
<file type="view" role="subview">./subviews/messages/no_js_alert.twig</file>
<file type="view" role="subview">./subviews/privacy/privacy.twig</file>
<file type="view" role="subview">./subviews/navigation/language_changer.twig</file>
<file type="view" role="subview">./subviews/logincomponents/captcha.twig</file>
<file type="view" role="subview">./subviews/logincomponents/token.twig</file>
<file type="css">./css/theme.css</file>
<file type="js">./scripts/theme.js</file>
<file type="css">./css/custom.css</file>
<file type="js">./scripts/custom.js</file>
</welcome>
<completed>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Completed')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="subview">./subviews/content/mainrow.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="content">./subviews/content/submit.twig</file>
<file type="css">./css/theme.css</file>
<file type="js">./scripts/theme.js</file>
<file type="css">./css/custom.css</file>
<file type="js">./scripts/custom.js</file>
</completed>
<assessments>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Assessments')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="subview">./subviews/content/mainrow.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="content">./subviews/content/submit.twig</file>
<file type="view" role="subview">./subviews/messages/assessments.twig</file>
<file type="css">./css/theme.css</file>
<file type="js">./scripts/theme.js</file>
<file type="css">./css/custom.css</file>
<file type="js">./scripts/custom.js</file>
</assessments>
<error>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Error')}} ]]></screen_title>
<file type="view" role="layout">layout_errors.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
</error>
<clearall>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Clear all')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="subview">./subviews/content/mainrow.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="content">./subviews/content/clearall.twig</file>
<file type="css">./css/theme.css</file>
<file type="js">./scripts/theme.js</file>
<file type="css">./css/custom.css</file>
<file type="js">./scripts/custom.js</file>
</clearall>
<load>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Load')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="subview">./subviews/content/mainrow.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="content">./subviews/content/load.twig</file>
<file type="css">./css/theme.css</file>
<file type="js">./scripts/theme.js</file>
<file type="css">./css/custom.css</file>
<file type="js">./scripts/custom.js</file>
</load>
<save>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Save')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="subview">./subviews/content/mainrow.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="content">./subviews/content/save.twig</file>
<file type="css">./css/theme.css</file>
<file type="js">./scripts/theme.js</file>
<file type="css">./css/custom.css</file>
<file type="js">./scripts/custom.js</file>
</save>
<register>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Registration')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="content">./subviews/content/register.twig</file>
<file type="view" role="subview">./subviews/registration/register_error.twig</file>
<file type="view" role="subview">./subviews/registration/register_head.twig</file>
<file type="view" role="subview">./subviews/registration/register_message.twig</file>
<file type="view" role="subview">./subviews/registration/register_success.twig</file>
<file type="view" role="subview">./subviews/registration/register_form.twig</file>
<file type="view" role="subview">./subviews/registration/required.twig</file>
</register>
<printanswers>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Print answers')}} ]]></screen_title>
<file type="view" role="layout">layout_printanswers.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="content">./subviews/content/printanswers.twig</file>
<file type="view" role="subview">./subviews/printanswers/printanswers_head.twig</file>
<file type="view" role="subview">./subviews/printanswers/printanswers_table.twig</file>
<file type="view" role="subview">./subviews/printanswers/printanswers_question.twig</file>
<file type="view" role="subview">./subviews/printanswers/printanswers_foot.twig</file>
</printanswers>
<statistics_user>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Public statistics')}} ]]></screen_title>
<file type="view" role="layout">layout_statistics_user.twig</file>
<file type="view" role="subview">./subviews/content/outerframe.twig</file>
<file type="view" role="content">./subviews/content/statistics_user.twig</file>
<file type="view" role="subview">./subviews/statistics_user/statistics_user_head.twig</file>
<file type="view" role="subview">./subviews/statistics_user/statistics_user_content.twig</file>
<file type="view" role="subview">./subviews/statistics_user/statistics_user_foot.twig</file>
</statistics_user>
<pdf>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('PDF')}} ]]></screen_title>
<file type="view" role="layout">layout_print.twig</file>
</pdf>
<quotas>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Quotas exceeded')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="content">./subviews/content/quotas.twig</file>
<file type="view" role="subview">./subviews/header/start_form.twig</file>
</quotas>
<navigation>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Navigation')}} ]]></screen_title>
<file type="view" role="layout">layout_global.twig</file>
<file type="view" role="subview">./subviews/footer/footer.twig</file>
<file type="view" role="content">./subviews/content/main.twig</file>
<file type="view" role="subview">./subviews/navigation/ajax_indicator.twig</file>
<file type="view" role="subview">./subviews/navigation/clearall_links.twig</file>
<file type="view" role="subview">./subviews/navigation/save_links.twig</file>
<file type="view" role="subview">./subviews/navigation/language_changer_top_menu.twig</file>
<file type="view" role="subview">./subviews/navigation/language_changer.twig</file>
<file type="view" role="subview">./subviews/navigation/question_index_menu.twig</file>
<file type="view" role="subview">./subviews/navigation/navigator.twig</file>
<file type="view" role="subview">./subviews/navigation/navigator_complement.twig</file>
<file type="view" role="subview">./subviews/navigation/clearall_buttons.twig</file>
<file type="view" role="subview">./subviews/navigation/save_buttons.twig</file>
<file type="view" role="subview">./subviews/navigation/question_index_buttons.twig</file>
<file type="view" role="subview">./subviews/navigation/question_index_questions_buttons.twig</file>
<file type="view" role="subview">./subviews/navigation/question_index_groups_buttons.twig</file>
</navigation>
<token>
<screen_title type="data" role="title" twig="on"><![CDATA[ {{gT('Participant')}} ]]></screen_title>
<file type="view" role="layout">layout_user_forms.twig</file>
<file type="view" role="content">./subviews/content/userforms.twig</file>
<file type="view" role="subview">./subviews/logincomponents/token.twig</file>
<file type="view" role="subview">./subviews/logincomponents/captcha.twig</file>
</token>
</screens>
<!-- Data for preview in Theme Editor and Twig Cache command line generator -->
<default_data>
<survey type="core">
<name type="data" twig="on"><![CDATA[ {{ gT("Template Sample") }} ]]></name>
<description type="data" twig="on"><![CDATA[<p>{{ gT('This is a sample survey description. It could be quite long.') }}</p><p>{{ gT("But this one isn't.") }}<p>]]></description>
<welcome type="data" twig="on"><![CDATA[<p>{{ gT('Welcome to this sample survey')}} <p> <p> {{ gT('You should have a great time doing this') }} <p> ]]></welcome>
<therearexquestions type="data" twig="on"><![CDATA[gT('There is 2 question in this survey'])]]></therearexquestions>
<surveyls_url type="data" twig="on">"https://www.limesurvey.org/"</surveyls_url>
<surveyls_urldescription type="data" twig="on"><![CDATA[ gT("Some URL description") ]]></surveyls_urldescription>
<showsurveypolicynotice>2</showsurveypolicynotice>
<datasecurity_notice_label type="data" twig="on"><![CDATA[ <a href='#data-security-modal-' data-bs-toggle='collapse'> {{ gT('Show privacy policy') }} </a> ]]></datasecurity_notice_label>
<datasecurity_notice type="data" twig="on"><![CDATA[ {{ gT("Your privacy policy text is shown here.") }} ]]></datasecurity_notice>
</survey>
<group type="core">
<name type="data" twig="on"><![CDATA[ {{ gT("Group 1: The first lot of questions") }} ]]></name>
<description type="data" twig="on"><![CDATA[ {{ gT("This group description is fairly vacuous, but quite important.") }} ]]></description>
</group>
<question_1 type="core">
<code type="data">'Q1 '</code>
<text type="data" twig="on"><![CDATA[ {{ gT("How many roads must a man walk down?") }} ]]></text>
<valid_message type="data" twig="on"><![CDATA[ <div id="vmsg_4496_num_answers" class="em_num_answers emtip error"><span class="fa fa-exclamation-circle" aria-hidden="true"></span> {{ gT("Choose one of the following answers") }} </div> ]]></valid_message>
</question_1>
<question_2 type="core">
<code type="data">'Q2 '</code>
<text type="data" twig="on"><![CDATA[ {{ gT("Please explain something in detail:") }} ]]></text>
<valid_message type="data" twig="on"><![CDATA[<div id="vmsg_4496_num_answers" class="em_num_answers emtip error"><span class="fa fa-exclamation-circle" aria-hidden="true"></span> {{ gT("Hint when response is not valid") }} </div> ]]></valid_message>
</question_2>
<assessments type="core">
<name type="data" twig="on"><![CDATA[ {{ gT("Welcome to the Assessment") }} ]]></name>
<message type="data" twig="on"><![CDATA[ {{ gT("You got {TOTAL} points out of 3 possible points.") }} ]]></message>
</assessments>
<!-- This is an example to show you how to add your custom screen in the theme editor with custom values -->
<!-- The name of the array inside aSurveyInfo that feed your twig view is specified as "array-name". If you check quotas.twig, you'll notice the main variable is aSurveyInfo.aQuotas -->
<!-- Notice that the data you pass here are simple. You can't pass complex arrays inside the array, only key => value pairs.-->
<quotas type="custom" arrayName="aQuotas">
<sMessage type="data" twig="on"><![CDATA[ {{ gT("Sorry your responses have exceeded a quota on this survey.") }} ]]></sMessage>
<sUrl type="data">http://limesurvey.org</sUrl>
<sUrlDescription type="data" twig="on"><![CDATA[ {{ gT("End url") }} ]]></sUrlDescription>
<bShowNavigator type="data">false</bShowNavigator>
</quotas>
<userforms type="custom" arrayName="aForm">
<sType type="data">token</sType>
</userforms>
</default_data>
</template_editor>
</engine>
<!-- Disable the updater system for core themes. -->
<updaters disabled="disabled">
</updaters>
</config>