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
Hello,
today I updated my Admin Panel to version 1.9.18. Now in the Pages section under the Advanced Tab and there in the Settings section, the HTML entities in the Parent-Page-List are no longer rendered properly, as you can see on the screenshot :
I think this is caused by the following commit : commit d01c959
Therefore I changed line 13 in public/user/plugins/admin/themes/grav/templates/forms/fields/pages/pages.html.twig from <option {% if page_route == value or (field.multiple and page_route in value) %}selected="selected"{% endif %} value="{{ page_route }}">{{ option }}</option>
to <option {% if page_route == value or (field.multiple and page_route in value) %}selected="selected"{% endif %} value="{{ page_route }}">{{ option|striptags|raw }}</option>
in my local installation.
It's no big issue, but for some editors it might be a bit confusing.
My environment :
Grav version : 1.6.30
Admin Panel : 1.9.18
PHP version : 7.4.13
Linux server
The text was updated successfully, but these errors were encountered:
Hello,
today I updated my Admin Panel to version 1.9.18. Now in the Pages section under the Advanced Tab and there in the Settings section, the HTML entities in the Parent-Page-List are no longer rendered properly, as you can see on the screenshot :
I think this is caused by the following commit : commit d01c959
Therefore I changed line 13 in public/user/plugins/admin/themes/grav/templates/forms/fields/pages/pages.html.twig from
<option {% if page_route == value or (field.multiple and page_route in value) %}selected="selected"{% endif %} value="{{ page_route }}">{{ option }}</option>
to
<option {% if page_route == value or (field.multiple and page_route in value) %}selected="selected"{% endif %} value="{{ page_route }}">{{ option|striptags|raw }}</option>
in my local installation.
It's no big issue, but for some editors it might be a bit confusing.
My environment :
The text was updated successfully, but these errors were encountered: