locale_string_is_safe should accept "<front>" as being safe

Open on Drupal.org →

Created on 12 September 2024, 6 months ago

Problem/Motivation

When a translatable string contains <front>, the \Drupal\locale\PoDatabaseWriter::importString reports an error, although this is a valid string in the Drupal world.

Proposed resolution

Remove that substring before testing the XSS filter.

🐛 Bug report

Status

Needs work

Version

11.0 🔥

Component

Last updated 4 days ago

Maintained by
🇭🇺Hungary @Gábor Hojtsy

Created by

🇩🇪Germany jurgenhaas Gottmadingen

Live updates comments and jobs are added and updated live.

Needs Review Queue Initiative
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.

Sign in to follow issues

Merge Requests

!9476locale_string_is_safe should accept "<front>" as being safe
Open
🇩🇪Germany jurgenhaas
updated 6 months ago

Comments & Activities

Issue created by @jurgenhaas
Merge request !9476Issue #3473763 by jurgenhaas: locale_string_is_safe should accept "<front>" as being safe → (Open) created by jurgenhaas
Status changed to Needs review 6 months ago8:08am 12 September 2024
Comment 6 months ago →
🇩🇪Germany jurgenhaas Gottmadingen
Pipeline finished with Success
6 months ago
Total: 429s
#280909
Status changed to Needs work 6 months ago1:49pm 12 September 2024
Comment 6 months ago →
🇺🇸United States smustgrave
Know it's a small change but since it's kinda around the XSS Filter code can we add test coverage. Believe there is a data provider somewhere could just add a new case for

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024