Bug #83721
closed
Page translated using localization overview is shown as normal page L=0
Added by Tymoteusz Motylewski about 6 years ago.
Updated about 4 years ago.
Category:
Backend User Interface
Description
In v9 when you translate a page using localization overview from the Info module
The page is create as a subpage of a given page instead of it's translation.
Translating a page uid =10, pid=5 results in page uid=11, pid=10, sys_language_uid= 0
- Description updated (diff)
- Category set to Backend User Interface
Still present on 9.2.0-dev
- Target version set to 9 LTS
- Target version changed from 9 LTS to Candidate for patchlevel
- Related to Bug #86181: Translation in the localisation overview creates pages instead of translations. added
- Status changed from New to Accepted
- Priority changed from Should have to Must have
- Target version changed from Candidate for patchlevel to 9 LTS
better description in duplicate
Prerequisite: A system with two (probably more) languages.
Create a few pages in the default language.
Open the localisation overview in the info module.
Select some (or all) pages in the column of the second language (checkboxes).
Click on "Create new translation headers"-button at the top.
Enter the translated titles. (Somewhat difficult because you can't see the original title. This may be the first indicator of the problem).
Save
See that subpages have been created for the pages, but no translations.
Used TYPO3 Version is: 9.4
- Target version changed from 9 LTS to Candidate for patchlevel
This is a very nasty issue. This is related to the fact that we do this ugly "just localized" functionality (calling DataHandler and then redirecting to FormEngine via returnURL) which is broken now because we don't do pages_language_overlay now.
In the context of the Info => Localization Overview, we have to tackle that different - basically reworking the whole module IMHO.
possibility a) Rework module
- It is not possible to translate multiple records at once anymore but we introduce a button "Translate" for each langauge in each page.
possibility b) - rework "Just Localized" functionality
- We built a new pattern where edit document controller shows a new record translation before saving it - this has a bigger impact
- Has duplicate Bug #87490: New translations created using Info module are considered new pages added
Still present on 10.0.1.0
- Related to Bug #89436: module WEB > list: localize a page does not work correctly added
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Under Review
- Status changed from Under Review to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by