This should be solved, and needs a regression test as well.

It does not work only when the user update his own survey and introduce a quote in updating the comment. For new answers (insert) there is not bug.

Ah.

@nicolasgoudard : only when reload by token ? Or move previous/move next too ?

@ollehar : i take a look, i assign it to me (or not) before end of this afternoon.

OK : question encoding must be done by twig or by code ?

My opinion : by twig , never by code

I have checked again : in really, the bug happened when select from database before display, not in insert or update.
Scenario : when reload by token (clink on the link received by email) : the string is not well escaped before displayed (miss characters after the quote, including the quote), , so when you move previous or next, the string is not the good anymore in the database, after update.
sorry if I not speak English good, I hope you understand what I mean .

Then :https://github.com/LimeSurvey/LimeSurvey/pull/1414

Need Dev discussion (in my opinion) and to be documented for Question Theme dev.

@tparner : Maybe maybe you have an opinion ? Value encoded or not ?

@nicolasgoudard : no need reloading :)

Previous do the trick

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

Thank you, Denis !

Can not update https://manualv4.limesurvey.org/Question_themes about text encoded.

@cdorin : can you check the manual ?

Dev: don't fix the param for previous questiontheme compatibility

fixed in 4.4.0 rc1