Can not test before https://github.com/LimeSurvey/LimeSurvey/commit/2547051b79fe41572b6cf3d5bf19ee61b7138f16#diff-c90402604812a00287877cafb2e02fda

Because at this commit id : jquery seems not loaded … and admin GUI didn't have way to edit question …

But it work good at https://github.com/LimeSurvey/LimeSurvey/commit/cfbe5975314dc031f63025f2e75f3df20d3aa4b5

ajaxify issue

Removing ajaxify.js fix the issue (hava another issue but after).
PS set ajax to NO didn't remove ajaxify call

Capture du 2018-03-17 00-02-34.png (32,145 bytes)   

Capture du 2018-03-17 00-02-34.png (32,145 bytes)   

I can't reproduce this.
You are sure you haven't changed anything?

Yes, git reset + git pull.

Can't reproduce it either.
Can you reproduce using the demo?

No problem for me on a fresh install. Denis, can you try that too? Maybe it's something in your config that enables ajax mode?

$ cd LimeSurvey_master/
$ git reset --hard
HEAD is now at cd6e000 Updated translation: Polish by elissa
$ git pull
Already up-to-date.
$ touch assets/packages/pjax/.ok
$ rm assets/packages/pjax/.ok

OK on demo
https://master.sondages.pro/479923?newtest=Y&lang=en

javascript link :
<link rel="stylesheet" type="text/css" href="/assets/styles-public/lime-progress.css" />
<script type='text/javascript'>window.debugState = {frontend : (0 === 1), backend : (0 === 1)};</script><script type="text/javascript" src="/third_party/jquery/jquery-3.1.1.js" class="headScriptTag"></script>
<script type="text/javascript" src="/third_party/jquery/jquery-migrate-3.0.0.js" class="headScriptTag"></script>
<script type="text/javascript" src="/assets/packages/limesurvey/survey.js" class="headScriptTag"></script>
<script type="text/javascript" src="/assets/packages/template-core/template-core.js" class="headScriptTag"></script>
<script type="text/javascript" src="/assets/packages/bootstrap/bootstrap.js" class="headScriptTag"></script>
<script type="text/javascript" src="/themes/survey/vanilla/scripts/theme.js" class="headScriptTag"></script>
<script type="text/javascript" src="/themes/survey/vanilla/scripts/ajaxify.js" class="headScriptTag"></script>
<script type="text/javascript" src="/themes/survey/vanilla/scripts/custom.js" class="headScriptTag"></script>
<script type="text/javascript" src="/assets/scripts/survey_runtime.js" class="headScriptTag"></script>
<script type="text/javascript" src="/assets/scripts/admin/expression.js" class="headScriptTag"></script>
<script type="text/javascript" src="/assets/scripts/expressions/em_javascript.js" class="headScriptTag"></script>
<script type="text/javascript" src="/assets/scripts/nojs.js" class="headScriptTag"></script>
<script type="text/javascript">
/<![CDATA[/
LSvar={"bFixNumAuto":1,"bNumRealValue":0,"sLEMradix":".","lang":{},"showpopup":1,"startPopups":{},"debugMode":2};
/]]>/
</script>

debug at 2 AND 'force_xmlsettings_for_survey_rendering' => true,

Why are you deleting pjax? of course it won't work without it...

I create a file in directory + delete it after : I DON'T DELETE PJAX, please have a real look

To be sure to have last asset version

'force_xmlsettings_for_survey_rendering' => true, => false

Fix the issue for default, but not for “extended”

OBS: Using force_xmlsettings_for_survey_rendering also enables ajax mode (if ajax mode = on in config, which is the default value).

Arg, didn't know that : thanks

But issue really strange :

• Set to true since some week : broke ranking
• Set to false : fix ranking
• Set to true : ranking (default) seem fixed …

Updated bug report to reflect the real problem

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=26804

Markus : something i don't understand : why with DB it work ? You hav 2 different system for add/remove ? one for DB and one for install ?

Yes and now. Yes, the xml gets loaded via the Model TemplateManifest and the Database gets loaded via TemplateConfiguration.
The basis of both of them is TemplateConfig, which has most of the shared methods, but some are a bit different and thus seperated into the two systems.

The xml-based system just did not have the packages_to_load functionality implemented.

Release 3.5.4+180320