[16.0][OU-FIX] website: Do BS conversion with sanitization override + Add website editors to sanitization override group#5216
Merged
pedrobaeza merged 2 commits intoOCA:16.0from Jul 26, 2025
Conversation
Certain fields had sanitize=False or other sanitization disablings (like sanitize_attributes=False or sanitize_form=False), so when converting to BS 5, we should allow to save the result without re-sanitizing such content. For that, if the user is not on the sanitize overridable group, we add it, removing it after conversion.
Website editors that come from v15, where there was no sanitization, would expect the same on the new version, or worst: they introduced some content like iframe in 15, and re-editing that content in 16 leads to lose it when saving it. Thus, let's add all of them to the override sanitization group for keeping the same behavior.
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
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.
@Tecnativa