Fixed #25283 -- Avoid collectstatic errors if an url contains a fragment that looks like a path #5642
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
…ent that looks like a path In some cases an @font-face declaration will contain a fragment that looks like a relative path. e.g. @font-face { src: url('../fonts/font.svg#../path/like/fragment'); } In these cases an incorrect path was passed to the storage backend, which raised an error that in turn caused collectstatic to stop dead in it's tracks.
|
merged in 7624fdb, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
In some cases an @font-face declaration will contain a fragment that looks like a relative path.
e.g. @font-face { src: url('../fonts/font.svg#../path/like/fragment'); }
In these cases an incorrect path was passed to the storage backend, which raised an error
that in turn caused collectstatic to stop dead in it's tracks.