You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a quotation is entered into a text element of an instrument (not text area element), and then saved, the element is saved properly but does not display on the front end. Here are some screenshots for an example:
This is because of how the HTML element is rendered: <input name="pulmonary_issues_specific" type="text" class="form-control input-sm" value="testing mid-"quotes"" >
This is not an issue for any other HTML special chars.
To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):
Go to medical history instrument in the raisinbread data (or another instrument that has text element)
Attempt to save values in quotations
Save
See that the value is saved properly in the back end, but does not display properly on the front end.
…#7776)
This fixes the escaping issue that occurs when a text field in an instrument contains an HTML special character. The solution employed here is to redirect on successful save to reload data directly from the database instead of loading it using the _POST data.
This solution is sub-optimal because the escaping issue will still occur when an error is detected on instrument save and the values MUST be reloaded from the _POST array where the reload can not occur to avoid losing the unsaved data.
Alternate to: #7777Fixes#7489
Replaces #7490
Describe the bug
When a quotation is entered into a text element of an instrument (not text area element), and then saved, the element is saved properly but does not display on the front end. Here are some screenshots for an example:
This is because of how the HTML element is rendered:
<input name="pulmonary_issues_specific" type="text" class="form-control input-sm" value="testing mid-"quotes"" >
This is not an issue for any other HTML special chars.
To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):
Additional context
Issue & PR made on CCNA
The text was updated successfully, but these errors were encountered: