Remove HTML entities from post slug during cleaning #68813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This PR ensures that HTML entities, such as
&
, are properly decoded when generating post slugs. It modifies thegetEditedPostSlug
selector to decode entities in post titles before cleaning them for slug creation.Why?
The current implementation adds unnecessary HTML entities like amp to slugs when saving drafts. This behavior can cause confusion and lead to unnecessarily long or SEO-unfriendly URLs. For example, a draft title containing
&
becomes/ampersand-amp-and/
, but upon publishing, it correctly becomes/ampersand-and/
. This PR fixes the inconsistency by decoding HTML entities before cleaning the slug.Fixes #62543
How?
Code changes are minimal and located in
packages/editor/src/store/selectors.js
.Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast