fix: handle relative links in cms content #1543
Merged
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.
PR Type
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
[ ] Other:
What Is the Current Behavior?
When inserting a link with a relative path to a Free Style HTML Component via TinyMCE (Full Mode) in the ICM backoffice, displaying this component in the PWA lead to a wrong absolute path, as the PWA host is set instaead of the ICM base URL.
This works without any issues when inserting images instead of links.
Issue Number: Closes #
What Is the New Behavior?
Relative paths of free style HTML components are handled correctly.
Does this PR Introduce a Breaking Change?
[ ] Yes
[x] No
Other Information
see also AB#91284
AB#91696