Version 3.17.6+190624 ?
Fixed here : https://github.com/LimeSurvey/LimeSurvey/commit/5e262a6901848a03430d814bba8e9d55f3a239f9#diff-fbd9719c3b6c1b87eefda2ed75d7c560

Can not reproduce with vanilla or bootswatch or fruity (or skelvanilla).

Can you check with included theme ?

Hi Denis

I have confirmed that the my answer_td_checkboxes.twig file are the same as the version on github. But the problem still persists.
I have checked this in Stock fruity and vanilla and the problem is the same. I am attaching the LSS we are using and the screen images.

Hope this helps.

Vanilla.jpg (31,253 bytes)   

Vanilla.jpg (31,253 bytes)   

Fruity.png (32,442 bytes)   

Fruity.png (32,442 bytes)   

Maybe reset assets ?

Can you check with array radio too ?
https://github.com/LimeSurvey/LimeSurvey/commit/4a99f4026309ed6fbba58587963dd76d5db09ba5

Hi Denis,

Sorry for delay, I have been away. How do you reset assets?

In global settings : you have a button

Thanks Denis,
Cleared the Cache and spotted an update to v3.17.7+190627 so have applied this too.
Also, cleared cache, cookies and emptied the tmp/assets folder for good measure.

Sadly the problem still persists on a new survey created today. Array Numbers - CheckerBox Display On.

Interestingly: Array Radio (Array by Column) and Array Numbers without setting the CheckerBox Switch do work as they should - so its only when you switch on the checkerbox display.

Hope this helps.

Screenshot 2019-07-09 at 20.20.34.png (98,842 bytes)   

Screenshot 2019-07-09 at 20.20.34.png (98,842 bytes)   

Screenshot 2019-07-09 at 20.30.48.png (38,261 bytes)   

Screenshot 2019-07-09 at 20.30.48.png (38,261 bytes)   

Screenshot 2019-07-09 at 20.32.36.png (35,080 bytes)   

Screenshot 2019-07-09 at 20.32.36.png (35,080 bytes)   

Really don't understand …
Can you check the files at : application/views/survey/questions/answer/arrays/multiflexi/rows/cells/answer_td_checkboxes.twig.

Maybe something related to twig cache ?
If you can : can you check the timestamp of this file ?

Can you send us a link (private mode if needed)

@DenisChenu - I have installed a new copy of LS and this is now working. So I agree this is a cache issue. Its still a problem but I will now investigate this more.

@LouisGac : do you know if Yii cache can produce such error ?
There are a way to force reset all Yii cache after ComfortUpgrade ?

I don't see any reason why Twig cache would cause this problem.
If nobody else face the problem, I'd rather bet on a serie of wrong manual updates + custom theme. Hard to say.

I don't see any reason why Twig cache would cause this problem.

Twig use file system for caching :) i don't know how and when this cache was updated. I can look, but maybe you already know ;)

Indeed the twig cache system is famous for being obscure and poorly documented.
Anyway: what we could do is to delete twig cache after an update.

Indeed the twig cache system is famous for being obscure and poorly documented.

lol ! mdr ! pdtr !

Anyway: what we could do is to delete twig cache after an update.

@marcgold : can you just delete tmp/runtime/twig_cache/ content and see if it's OK on the broken system ?

Also, if the user upload the files from a dev server to a production server, it could be related to this issue:
https://github.com/twigphp/Twig/issues/2498

Btw: you can see the user clearly says that Twig Documentation for the Cache system is incomplete and wrong.
I will check if we're using realtive or absolute path.

Yes :)

But clearing tmp/runtime/twig_cache/* can be OK. Then we just need to clear one after ComfortUpgrade (and maybe create a command action)

Let's wait for User answer about manually deleting :)

@DenisChenu - You cracked it. Deleting the twig_cache resolved the problem.

marcgold: could you tell us how did you update? are you updating a local installation, and then pushing your files to a production server via ftp?

@LouisGac - No we always update using the comfort update. We take a backup first just incase. Have always found the comfort update to be very reliable.

ok thank you. We'll add a "delete twig cache" after update then.

You're using an outdated version of LimeSurvey. Please update to the latest version and check if the bug can still be reproduced. Thank you.

Hello marcgold,

we have asked for feedback on this issue. Because we did not get an answer we assume that the issue is resolved.
However, should you be able to reproduce the issue using the latest version, please feel free to re-open the issue and give us exact details on how to reproduce it.

Thank you and best regards,

c_schmitz