Feature #28441

Backend should (easily) allow to switch language used in page-tree

Added by Stefan Neufeind about 8 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2011-07-25
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

If you use pages with language-overlays the pagetree just displays titles from the default-language.

Example: Default-language is English but the person is working on the Spanish translation of the website. He/she can decide which page-language to edit on the right (main) side in the backend. But the page-tree always displays the default page-titles.


Related issues

Related to TYPO3 Core - Bug #18565: Translation of the backend pages tree Closed 2008-04-04
Related to TYPO3 Core - Bug #24351: Page Module "Show page language version" and page tree Closed 2010-12-17
Related to TYPO3 Core - Feature #46017: Language switcher for pagetree in Backend New 2013-03-04

History

#1 Updated by Georg Ringer about 8 years ago

see maybe EXT:fb_hybridmultilanguagetree

#2 Updated by Ingo Renner about 8 years ago

I remember Mattes had an extension for that too... dunno what its status is though

#3 Updated by Henrik Ziegenhain about 8 years ago

Georg Ringer wrote:

see maybe EXT:fb_hybridmultilanguagetree

I think this extension doesn`t work properly with the new pagetree.

#4 Updated by Andreas Wolf about 8 years ago

  • Category set to Backend User Interface

#5 Updated by Steffen Ritter almost 8 years ago

  • Target version set to 4.7.0-alpha3

#6 Updated by Steffen Ritter over 7 years ago

  • Target version changed from 4.7.0-alpha3 to 4.7.0-beta1

#7 Updated by Steffen Ritter over 7 years ago

  • Target version deleted (4.7.0-beta1)

#8 Updated by Felix Kopp almost 5 years ago

  • Status changed from New to Accepted

#9 Updated by Riccardo De Contardi almost 4 years ago

  • Status changed from Accepted to Closed

I close this, as the feature is being developed with #46017; please continue the discussion or give your contribution there.
I'll relate this to #46017 to keep track of it

If you think that this is the wrong decision , then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Also available in: Atom PDF