[FIX] 48047: Änderungen im Content Style wirken sich nicht aus - #11833
Merged
chfsx merged 1 commit intoJul 28, 2026
Merged
Conversation
Entries inside a container are stored relative since Mantis 45580 / 47237, e.g. "style.css". Containers written before that hold the same file as "/style.css", and once such a container is written again both variants exist side by side. Streams::ofFileInsideZIP() looked up the variant with the leading slash first, so consumers kept receiving the outdated legacy entry: a content style is written correctly but never changes for the user. Newly created styles are not affected, copies inherit the problem with the cloned ZIP, and export/import produces a clean container. ofFileInsideZIP() now looks up the relative entry first and falls back to the legacy one, which fixes existing containers without touching them - the ZIP stream wrapper matches entry names literally, so no container can be resolved to the wrong entry by accident. Additionally the legacy entries are cleaned up over time: addUploadToContainer() no longer produces entries with a leading slash itself when the parent path inside the container is empty, and removePathInsideContainer() removes both variants of the given path.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Entries inside a container are stored relative since Mantis 45580 / 47237, e.g. "style.css". Containers written before that hold the same file as "/style.css", and once such a container is written again both variants exist side by side. Streams::ofFileInsideZIP() looked up the variant with the leading slash first, so consumers kept receiving the outdated legacy entry: a content style is written correctly but never changes for the user. Newly created styles are not affected, copies inherit the problem with the cloned ZIP, and export/import produces a clean container.
ofFileInsideZIP() now looks up the relative entry first and falls back to the legacy one, which fixes existing containers without touching them - the ZIP stream wrapper matches entry names literally, so no container can be resolved to the wrong entry by accident.
Additionally the legacy entries are cleaned up over time: addUploadToContainer() no longer produces entries with a leading slash itself when the parent path inside the container is empty, and removePathInsideContainer() removes both variants of the given path.