Bug #30469
closedSorting of localized tt_content elements is wrong after copying
100%
Description
When copying a content element on a page with two or more languages, the pasted element will appear in the correct position on the target page whereas the localized partner elements will appear in the first (topmost) position above all other elements of this language.
Steps to reproduce:
1) Go to page A (Page needs to have two or more languages)
2) Copy one content element
3) Paste the element to page B below all other CEs (page B needs to have two or more languages and two or more content elements)
Result: The main language CE will be in the correct position while the pasted language overlay will appear in the first position above all already existing records.
Updated by Peter Niederlag almost 13 years ago
- Category set to DataHandler aka TCEmain
- Complexity set to medium
Updated by Peter Niederlag almost 13 years ago
- Status changed from New to Accepted
Updated by Jochen Rieger almost 13 years ago
We would like to sponsor this bugfix... please contact me per PM if you would like to fix it.
Updated by Stanislas Rolland almost 13 years ago
The page module allows to change the order of the elements in each language independently. Therefore the corresponding elements may be presented in each language in a completely different order. Is this a bug or a feature?
If a user pastes an element in the default language column, then where should the translated records of this element be inserted if the other translated records are not in the same order as the corresponding records in the default language?
Updated by Stanislas Rolland almost 13 years ago
Let us call "destination record" the record after which the copied record should be inserted.
When copying a record in original language, if a localized record of the destination record exists for language A, then the localized record of the copied record, if it exists for language A, should be inserted after the localized record, in language A, of the destination record.
The same applies when moving a record in original language: if a localized record of the destination record exists for language A, then the localized record of the moved record, if it exists for language A, should be inserted after the localized record, in language A, of the destination record.
Thus, if both the copied/moved record and the destination record have all translations possible for their pages, the localized records of the copied/moved record will be inserted after the localized records in the corresponding languages of the destination record.
Updated by Mr. Hudson almost 13 years ago
- Status changed from Accepted to Under Review
Patch set 1 of change If01e602b0fe68423baba9f9973bd5237c1d0b75a has been pushed to the review server.
It is available at http://review.typo3.org/6032
Updated by Mr. Hudson almost 13 years ago
Patch set 1 of change If01e602b0fe68423baba9f9973bd5237c1d0b75a has been pushed to the review server.
It is available at http://review.typo3.org/6038
Updated by Chris topher almost 13 years ago
- Target version changed from 4.5.7 to 4.5.8
Updated by Mr. Hudson almost 13 years ago
Patch set 1 of change I78f1703db536bfabb64087f5e3e2064dc09b9eb2 has been pushed to the review server.
It is available at http://review.typo3.org/6380
Updated by Stanislas Rolland almost 13 years ago
- Assignee set to Stanislas Rolland
Updated by Stanislas Rolland almost 13 years ago
A similar situation may arise when a new localization record is created. Patch set 2 will insert a new localized record in a given language after the localized record in the same language, if it exists, of the record, in default language, preceding the record being localized.
Updated by Mr. Hudson almost 13 years ago
Patch set 1 of change Id483de6ff1246e0f9587bdecb9548ec863706084 has been pushed to the review server.
It is available at http://review.typo3.org/6406
Updated by Mr. Hudson almost 13 years ago
Patch set 1 of change I7e95268e159f5c652c1c99b9663293e3a7ff9096 has been pushed to the review server.
It is available at http://review.typo3.org/6407
Updated by Mr. Hudson almost 13 years ago
Patch set 2 of change If01e602b0fe68423baba9f9973bd5237c1d0b75a has been pushed to the review server.
It is available at http://review.typo3.org/6032
Updated by Mr. Hudson almost 13 years ago
Patch set 3 of change If01e602b0fe68423baba9f9973bd5237c1d0b75a has been pushed to the review server.
It is available at http://review.typo3.org/6032
Updated by Gerrit Code Review over 12 years ago
Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/6032
Updated by Gerrit Code Review over 12 years ago
Patch set 2 for branch TYPO3_4-6 has been pushed to the review server.
It is available at http://review.typo3.org/6406
Updated by Gerrit Code Review over 12 years ago
Patch set 2 for branch TYPO3_4-5 has been pushed to the review server.
It is available at http://review.typo3.org/6407
Updated by Gerrit Code Review over 12 years ago
Patch set 5 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/6032
Updated by Gerrit Code Review over 12 years ago
Patch set 3 for branch TYPO3_4-6 has been pushed to the review server.
It is available at http://review.typo3.org/6406
Updated by Gerrit Code Review over 12 years ago
Patch set 3 for branch TYPO3_4-5 has been pushed to the review server.
It is available at http://review.typo3.org/6407
Updated by Gerrit Code Review over 12 years ago
Patch set 6 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/6032
Updated by Stanislas Rolland over 12 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 89bd701c31a5620c934b5dc6ecfc8f5114a5c59d.
Updated by Stanislas Rolland over 12 years ago
- Status changed from Resolved to Under Review
- Target version changed from 4.5.8 to 4.5.12
Updated by Stanislas Rolland over 12 years ago
- Status changed from Under Review to Resolved
Applied in changeset cf3d4232cfd4090e840d18d4854d5d9da0e1bbd6.
Updated by Riccardo De Contardi almost 7 years ago
- Status changed from Resolved to Closed
Updated by Tobias Liebig over 6 years ago
- Related to Bug #83079: wrong sorting of content elements when translating using non-default-language CEs as source added