Project

General

Profile

Actions
Copy link

Bug #25254

closed

wrong position for newly created tt_content translations

Added by Viktor Livakivskyi over 13 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2011-03-03
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

  1. I have a multilingual 4.5.2 installation.
  2. First I create content element in default language, then in 'Languages' view of 'Page' module I press 'Copy default content elements' and unhide a copy. So far so good.
  3. Next I create one more content element below existing one in default language column and 'Copy default content elements' button appears again.
  4. I press the button, and a copy is created, but it is created at the top of the column - not below existing element, like default language version!

It makes wrong output for translated version and no way to fix it, when mod.web_layout.defLangBinding = 1 is set.

Looking at db I can see, that:
  • first CE in default language is created with '256' in 'sorting' field.
  • it's translation is created with '512' (shouldn't it be 256 too?)
  • next CE in default language is created with '384'
  • it's translation is with '448'

(issue imported from #M17862)

Actions
Copy link
 #1

Updated by Markus Klein over 12 years ago

  • Target version deleted (0)

Additionally the ordering of translated records is also destroyed when moving around elements in the list module.

Actions
Copy link
 #2

Updated by Markus Klein over 12 years ago

Still valid up to 4.7

IMO a must have!

Actions
Copy link
 #3

Updated by Markus Klein over 9 years ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback
  • Is Regression set to No

Since this never made its way into 4.5 and support phase is almost over, we need to check if this is still true for 6.2+

Actions
Copy link
 #4

Updated by Viktor Livakivskyi over 9 years ago

Hi, Markus.

Just checked it with 6.2.11 - issue still exists.

Actions
Copy link
 #5

Updated by Markus Klein over 9 years ago

  • Subject changed from 4.5 makes wrong position for newly created tt_content translations to wrong position for newly created tt_content translations
  • Category set to Backend API
  • Status changed from Needs Feedback to Accepted
Actions
Copy link
 #6

Updated by Markus Klein over 9 years ago

  • Priority changed from Should have to Must have
Actions
Copy link
 #7

Updated by Markus Klein over 9 years ago

  • Description updated (diff)
Actions
Copy link
 #8

Updated by Markus Klein over 9 years ago

Related function seems to be \TYPO3\CMS\Core\DataHandling\DataHandler::getPreviousLocalizedRecordUid()

Actions
Copy link
 #9

Updated by Markus Klein over 9 years ago

I'm failing to reproduce this on current master and also on 6.2.11

Actions
Copy link
 #10

Updated by Markus Klein over 9 years ago

oh I forgot to set defLangBinding

Actions
Copy link
 #11

Updated by Markus Klein over 9 years ago

Still even with defLangBinding = 1 I fail to reproduce this.

Actions
Copy link
 #12

Updated by Viktor Livakivskyi over 9 years ago

Armed with Xdebug and Phpstorm I've found, that in my currnet case the reason was in EXT:Flux, which changes sorting by a hook.
So, I'll communicate this issue to the extensions authors.
TYPO3 is clean and issue can be closed :)

Actions
Copy link
 #13

Updated by Markus Klein over 9 years ago

  • Status changed from Accepted to Closed

Thanks for the feedback.

Actions
Copy link

Also available in: Atom PDF