Bug #82521
closed
Links to a mounted page in a page tree with a different domain are not prepended with the domain
0%
Description
If you link to a page in another page tree with a different domain, the link gets prepended with the domain of the other page tree. But if the target page mounts another page, then the domain is not prepended. It seems like, as soon as the link has the GET parameter MP, the rootline check is not done.
This happens on typolinks, but also in menus and links from the RTE. Tested TYPO3 Versions are 6.2, 7.6 and 8.7.
A detailed testcase is attached.
Files
Updated by Marco Huber about 7 years ago
The "id wrong and MP missing" errors in the Excel file are somehow ok, but critical is the "Domain missing" in row 17 and 18.
Updated by Tymoteusz Motylewski almost 7 years ago
- Category changed from Pagetree to Site Handling, Site Sets & Routing
Updated by Susanne Moog about 6 years ago
- Sprint Focus set to On Location Sprint
Updated by Susanne Moog almost 5 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Susanne Moog almost 5 years ago
- Sprint Focus set to On Location Sprint
Updated by Benni Mack almost 5 years ago
- Status changed from New to Needs Feedback
Hi Marco,
I think this will be solved with https://review.typo3.org/c/Packages/TYPO3.CMS/+/62878 - can you try out the patch?
Updated by Benni Mack almost 5 years ago
- Related to Bug #86331: Mountpoints not working with new site configurations added
Updated by Marco Huber almost 5 years ago
Is there a way to disable the new routing feature so I can get back the old index.php?id=123 URLs?
Updated by Marco Huber almost 5 years ago
It seems like the cross-tree/domain-links with mountpoints are working with the patch in TYPO3 9.5, so I think you can close this ticket. Thank you!
Updated by Riccardo De Contardi almost 5 years ago
- Status changed from Needs Feedback to Closed
@Markijan no-lastname-given Huber thank you for your time; closed.
If you think that this is the wrong decision or experience the issue again please reopen it or open a new issue with a reference to this one. Thanks again.