Feature #22113
closed
Possibility to link to an explicit language of a page
Added by Sonja Schubert over 14 years ago.
Updated about 4 years ago.
Category:
Backend User Interface
Description
Sometimes it's necessary to link to an explicit language version of a page. At the moment you have to do it with an external url link.
It would be better, if you can choose in the typolink popup which language version you want to link.
We've solved that problem with the extension cabag_langlink, which is in TER and on FORGE.
http://forge.typo3.org/projects/show/extension-cabag_langlink
But it would be great if that would become part of the core/rtehtmlarea. Of course I can create a patch, but I'm not shure about the way of change in browse_links.php
(issue imported from #M13524)
- Description updated (diff)
- Category set to Backend User Interface
- Status changed from New to Accepted
- Target version changed from 0 to 7.0
- PHP Version changed from 5.2 to 5.5
Related to the whole locale stuff.
- Target version changed from 7.0 to 7.1 (Cleanup)
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
- Target version changed from 7.5 to 8 LTS
- Target version changed from 8 LTS to 9.0
- Status changed from Accepted to Needs Feedback
- Target version deleted (
9.0)
As far as I can see, this can already be achieved since quite some time when using Page TSConfig:
RTE.default.buttons.link.queryParametersSelector.enabled = 1
(not specific for language but enables to use all kinds of parameters, which I consider "enough" to solve this use case.)
The solution proposed by Susanne Moog seems to work with both 8.7.13 and 9.3.0-dev (latest master), but there are some usability issues
1) on the select link wizard you have to write &L=1 (for example) inside the "Additional link parameters" field so the editor must know what parameter is needed and its syntax
2) on the select link wizard, you must write &L=1 inside the "Additional link parameters" field before choosing the page, or the wizard popup will close and the procedure must be repeated :)
3) if you edit the link opening again the wizard, the field "Additional link parameters" results empty (wrong)
4) your editor must know beforehand that the page is translated
- Related to Feature #87836: Can not link to translated page throug Link Browser. added
- Related to Bug #90100: Linking cross-site to page uid with different languages doesn't work added
- Status changed from Needs Feedback to Closed
The usability issues are independent of the feature request. For the core, I consider the existing possibilities as enough for the usual use cases. For more specific use cases there are extensions that can be used or customized.
@Susanne Moog
Apart from the usability issues,
3) if you edit the link opening again the wizard, the field "Additional link parameters" results empty (wrong)
This is quite a problem; I will test again and open a new issue. Regards.
I repeated the test on my comment 8 with 10.4.0-dev and 9.5.14
1) on the select link wizard you have to write &L=1 (for example) inside the "Additional link parameters" field so the editor must know what parameter is needed and its syntax
2) on the select link wizard, you must write &L=1 inside the "Additional link parameters" field before choosing the page, or the wizard popup will close and the procedure must be repeated :)
3) if you edit the link opening again the wizard, the field "Additional link parameters" results empty (wrong)
4) your editor must know beforehand that the page is translated
Results:
1) Still true (obviously)
2) Still true; plus, if you click somewhere else on the tree in the wizard, the field will empty itself
3) Not true, the &L=1 is kept
4) Still true (obviously)
- Related to Feature #90825: link to an explicit language of a page - usability issue added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by