Fix non-English characters being url encoded in breadcrumb #3819
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
silvio2402
suggested changes
Aug 16, 2022
There was a problem hiding this comment.
Hey @dilless, thank you for taking your time to contribute to the minimal-mistakes theme.
Your change looks good to me, however, you can remove the | replace: '%20', ' ' because %20 is now being url decoded anyways.
|
@silvio2402, thank for your checking. I have removed |
minyoongi96
pushed a commit
to minyoongi96/minyoongi96.github.io
that referenced
this pull request
Aug 26, 2024
…#3819) * Fix non-English characters being url encoded in breadcrumb * Remove `| replace: '%20', ' ‘`
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
This is a bug fix.
Summary
Non-English characters being url encoded in breadcrumb navigation.
I added url_decode filter in breadcrumb navigation link text to fix that
Context
Tis related to my discussion #3816