Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.
I was not succesful in fixing this issue.
I tried regular editing, pop-up editor Html plain and pop-up HTML editor within in "code modus".
All with the same result: no errors in QA Logic file, but errors during run-time.
Indeed, system detects the HTML-code for ': & # 039.
But even though I delete manually the original ' with a new ': no success.
Perhaps something within the settings: disable inline HTML-editor???
Or: can I use a plain editor externally and then copy plain code to the editor?
Can I use an external editor, and change the code to UTF-8, or something?
Is there a way to look "under water" if the HTML-code is being used, before testing
(testing is cumbersome, since I have to go to bunch of questions before I arrive at the question with the troubled code).
I just test with a 2.05 version with HTML editor on : really no problem.
In last GIT version : no problem too (HTML editore with/without XSS)
What is your LS version ?
Think best is to deactivate inline HTML editor
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.
The pop-up HTML-editor doesn't really save the changes.
If you make changes within the pop-up HTML-editor, and then save within the HTML-editor,
and run QA logic file, the changes are not shown.
You have to close the pop-up HTML-editor, and then push "Save" in the main screen, to actually save the changes.
It might be that the HTML-codes are incorporated once more once you save in the main screen.
*** solved ***
I solved the issue with a workaround.
The error was triggered by using the ' in a subquestion.
I used a 'subscription'.
The system detected HTML-code, which could not be resolved.
I introduced an additional field, with the use of a equation question, so the field subscription with the value subscription.
In the subquestion I no longer used a string between the ' and ',in this case 'subscription' but used the newly introduced equation field {subscription}