Bug #95372
closed
Avoid referencing public assets across packages
100%
Description
Since TYPO3 core packages (extensions) are independently
published and might be installed in arbitrary file locations
in the near future, referencing assets in package A
from a CSS file package B will likely not work.
Therefore all assets that are referenced from a CSS
file are now moved to the package that contains this CSS file.
Also references of assets in CSS that already were located
in the same package are cleaned up to not assume a hard coded
path name (breaking out of Resources/Public directory).
Updated by Gerrit Code Review about 3 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/71332
Updated by Gerrit Code Review about 3 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/71332
Updated by Gerrit Code Review about 3 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/71332
Updated by Helmut Hummel about 3 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 0c692a4ec40747770ef2fafe0296e4a59cc53ccb.
Updated by Oliver Bartsch about 3 years ago
- Related to Bug #95388: errorpages.css is always loaded in backend added
Updated by