Bug #100661
closed
Wrong resource links to symlinked _assets unsing base with appending path segment
0%
Description
TYPO3 v12.3.0
typo3/cms-composer-installers:5.0.0
Site Config base https://mydomain.com/path/
Reproduce for example with fluid like this:
<f:uri.image src="EXT:vendor_sitepackage/Resources/Public/Images/Logo.svg"/>
This results in an exceptions since the resolved path is "/path/_assets/5bd5aaeffedb0553dcc3d3be99b60d08/Images/Logo.svg" instead of "/_assets/5bd5aaeffedb0553dcc3d3be99b60d08/Images/Logo.svg".
Updated by Anonymous about 1 year ago
HINT: In general we should use uri:resource ViewHelper for assets outside a FAL storage. So replacing the ViewHelper solves the problem in that case.
But I still think there is a problem somewhere in a deeper level (maybe in PathUtility). Pathes should be resolved correctly also with a appending path in baseURL. Before the _asset symlinking this worked just fine.
Updated by Benni Mack 11 months ago
- Target version changed from 12 LTS to Candidate for patchlevel
Updated by Garvin Hicking 8 months ago
- Related to Bug #101911: TYPO3 composer mode does not properly respect installations in a subdirectory added
Updated by Markus Klein about 14 hours ago
ยท Edited
This seems to be a duplicate of #96887
wrong issue, sorry
Updated by Markus Klein about 14 hours ago
- Is duplicate of Task #96887: Allow only Resources/Public in PathUtility->getPublicResourceWebPath added
Updated by Markus Klein about 14 hours ago
- Status changed from New to Closed
- Target version deleted (
Candidate for patchlevel)
Updated by Markus Klein about 14 hours ago
- Is duplicate of deleted (Task #96887: Allow only Resources/Public in PathUtility->getPublicResourceWebPath)
Updated by Markus Klein about 14 hours ago
- Status changed from Closed to Accepted
Updated by Markus Klein about 14 hours ago
- Is duplicate of Bug #103157: Image referenced by `EXT:` does not work in TYPO3 subfolder installation added
Updated by Markus Klein about 14 hours ago
- Status changed from Accepted to Closed