Bug #80903
closed
Relative links with old <link> syntax are not converted to <a href> in upgrade wizard and not supported in ckeditor or linkfields
Added by Patrick Lenk over 7 years ago.
Updated over 2 years ago.
Category:
Site Handling, Site Sets & Routing
Description
It seems that relative links in richtext and text fields with old <link> syntax are not converted to <a href> in upgrade wizards row updater task "Scan for old "<link>" syntax in richtext and text fields and update to "<a href>"".
We have a multidomain environment with a data pool of pages. This pages are referenced in different domains (own pages with referenced contents from the data pool pages).
In the data pool there are content elements (teasers), the teasers have relative links to this pages. The teasers are also referenced in different domains.
You want to link the pages in the teasers at the same time for all domains, without linking any page to there own page id.
Here we use relative links like <a href="microsite123/>Deeplink</a>. This links are stored in database like <link microsite123/>Deeplink</link>.
The upgrade wizard task ignores this links. In frontend this links are rendered, but in ckeditor this links are not visible or not rendered from database. So the backend user doesn't know if there is a link or not.
It would be nice if the upgarde wizard taks convert this links to.
Also it would be nice if TYPO3 supports the tel: link protocol or simply allow links with tel in rte. See Issue https://forge.typo3.org/issues/80217
Thanks!
- Subject changed from Relative links in old <link> syntax are not converted to <a href> in upgrade wizard to Relative links with old <link> syntax are not converted to <a href> in upgrade wizard
- Category changed from RTE (rtehtmlarea + ckeditor) to Install Tool
Relative links like "microsite/" are also not implemented in the new link fields, but this is maybe a further issue.
Update: It seems that the old internal-link handling is also dropped in rte_ckeditor. Its not possible to set relative/realurl links (no aliases) to internal pages in a multidomain environment like descripted above. The old rte links are rendered in frontend via legacy link converter, but new links can not set, ckeditor or the core linkservice can not handle relative links without any url scheme.
- Category changed from Install Tool to RTE (rtehtmlarea + ckeditor)
- Subject changed from Relative links with old <link> syntax are not converted to <a href> in upgrade wizard to Relative links with old <link> syntax are not converted to <a href> in upgrade wizard and not supported in ckeditor or linkfields
Problem summary:
- old relative internal links not converted to new link syntax in ckeditor, in frontend they converted
- relative internal links are not supported in ckeditor / url linkhandler
- url linkhandler adds scheme to every link (relative internal links and external links)
- url linkhandler adds backend domain to every link without scheme
- url linkhandler adds _blank target value to every link, if extTarget is set in constants (relative internal links and external links)
Are there any plans for relative links in v8 LTS?
- Category changed from RTE (rtehtmlarea + ckeditor) to Site Handling, Site Sets & Routing
- Assignee set to Benni Mack
When will this bug be fixed? It's a must have to be able to set internal links in rte/ckeditor.
#1460629247: No valid handlers found for type: unknown
TYPO3\CMS\Core\LinkHandling\Exception\UnknownLinkHandlerException thrown in file
typo3/sysext/core/Classes/LinkHandling/LinkService.php in line 154.
- PHP Version changed from 7.0 to 7.2
- Related to Epic #84726: Initiative: URL Routing Integration / Site Handling added
- Related to Bug #80217: CKeditor: No valid handlers found for type: tel added
- Sprint Focus set to On Location Sprint
- Target version changed from next-patchlevel to Candidate for patchlevel
- TYPO3 Version changed from 8 to 9
Is there any time line for this bug? In TYPO3 9 the problem got worse because the relative links in <link> vanish from the frontend completely. We do have 6 to 7.000 of such links in our installation ...
- Sprint Focus deleted (
On Location Sprint)
Is there a solution for this bug? (As long as this is not resolved, I cannot update to LTS9 with ckeditor). Please allow/support relative links with ckeditor.
Is this related or even the same issue? #83683
Riccardo De Contardi wrote:
Is this related or even the same issue? #83683
yes
- Related to Bug #83683: Upgrade wizard for TYPO3 8 don't migrate "<link" to "<a href" if there is no link protocol added
- TYPO3 Version changed from 9 to 10
The bug still exists in v10.4 when migrating from v7
The things that did not get converted look like this:
<link http://example.de/marine-sensorsysteme>Arbeitsgruppe "Marine Sensorsysteme"</link>
<link http://example.de/marine-sensorsysteme>Arbeitsgruppe "Marine Sensorsysteme"</link>
<link http://example.de/cod>Projekt "Coastal Ocean Darkening"</link>
<link http://example.org>EyeOnWater: App und Datenbank</link>
<link http://example/science-strategy-publications>Positionspapier "Advancing Citizen Science for Coastal and Ocean Research" <br /></link>
I assume the " might have been a problem or something else which prevented the conversion.
- Status changed from New to Closed
Yes. Unfortunately there is nothing we can do there anymore from TYPO3-Core-Community side as the Row Updater is not available anymore in TYPO3 Core v10 + v11. I don't know if the ELTS is willing to fix this, but this could be fixed in an public extension like this: https://extensions.typo3.org/extension/core_upgrader
I'm very sorry for the late answer and that we did not fix this in Core!
I don't know why and since when, but relative links like href="/subpage/landingpage/"
seems to work again in ckeditor and TYPO3 v10.4.
Also available in: Atom
PDF