Bug #16949
closed
Absolute links are made relative which breaks link
Added by Rickard Andersson almost 18 years ago.
Updated about 6 years ago.
Description
I have multiple subdomains hosted in the same Typo3 install. On certain pages, I need to do links in the RTE that go across these subdomains. For example, on page www.sub1.domain.com, I want to link to a page on www.sub2.domain.com. To do this, I use the "External URL" tab of the htmlarea link popup and enter the full address to the page on the other subdomain. However, when I save the entry and typo3 runs it's RTE->DB transformation, that absolute URL gets transformed into a relative URL (for example <link 123>). This breaks the URL in the frontend because page 123 is a page under the other domain and can therefor not be accessed with a relative URL.
Currently, I have to manually edit the database entry every time someone updates it via the backend. NOT fun.
I'm not running realurl, simulatestaticdocuments or anything fancy like that. Just plain old vanilla index.php?id=123 type addresses.
(issue imported from #M4936)
Can someone please move this to the right project if tx_rtehtmlarea is wrong? I didn't see that drop-down in the upper right corner.
Yes. I've tried enabling it both in my tsconfig and in my template (wasn't sure if this was backend or frontend). No change.
I ran into the same problem but found a work around and possible a way to solve this. The URL being saved into the database depends on the URL of you're back-end. If you log in to the Typo3 backend from the domain the site belongs to, it's working fine. Edit content on www.sub.com from www.sub.com/typo3 and content for www.main.com from www.main.com/typo3. You're always in the same backend but the external URL's being generated (to www.main.com and www.sub.com) are now correct.
When generating links to an external website, HTMLArea seems to look at the URL of the backend to determine whether it's a link to an external site or not. HTMLArea should look at the domain records in the root of the page tree instead.
Same problem, work around works..
excactly the same problem here. workaround works but that's not very nice. is this bug ever gonna fixed?
This is a duplicate of #9455.
- Status changed from Resolved to Closed
Also available in: Atom
PDF