Feature #22113

Possibility to link to an explicit language of a page

Added by Sonja Schubert over 10 years ago. Updated 7 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2010-02-12
Due date:
% Done:

0%

PHP Version:
5.5
Tags:
Complexity:
Sprint Focus:

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)


Related issues

Related to TYPO3 Core - Feature #87836: Can not link to translated page throug Link Browser. Closed 2019-03-04
Related to TYPO3 Core - Bug #90100: Linking cross-site to page uid with different languages doesn't work New 2020-01-13
Related to TYPO3 Core - Feature #90825: link to an explicit language of a page - usability issue New 2020-03-24

History

#1 Updated by Mathias Schreiber almost 6 years ago

  • 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.

#2 Updated by Mathias Schreiber almost 6 years ago

  • Target version changed from 7.0 to 7.1 (Cleanup)

#3 Updated by Benni Mack over 5 years ago

  • Target version changed from 7.1 (Cleanup) to 7.4 (Backend)

#4 Updated by Susanne Moog about 5 years ago

  • Target version changed from 7.4 (Backend) to 7.5

#5 Updated by Benni Mack about 5 years ago

  • Target version changed from 7.5 to 8 LTS

#6 Updated by Riccardo De Contardi over 3 years ago

  • Target version changed from 8 LTS to 9.0

#7 Updated by Susanne Moog over 2 years ago

  • 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.)

#8 Updated by Riccardo De Contardi over 2 years ago

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

#9 Updated by Riccardo De Contardi over 1 year ago

  • Related to Feature #87836: Can not link to translated page throug Link Browser. added

#10 Updated by Riccardo De Contardi over 1 year ago

I report here that there is an extension that might be of help: https://github.com/CMSExperts/link2language

#11 Updated by Riccardo De Contardi 8 months ago

  • Related to Bug #90100: Linking cross-site to page uid with different languages doesn't work added

#12 Updated by Susanne Moog 7 months ago

  • 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.

#13 Updated by Riccardo De Contardi 7 months ago

@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.

#14 Updated by Riccardo De Contardi 7 months ago

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)

#15 Updated by Riccardo De Contardi 7 months ago

  • Related to Feature #90825: link to an explicit language of a page - usability issue added

Also available in: Atom PDF