TYPO3 Core

To make things easyer, one could set the sorting value of the translated elements always to the same value as the corresponding default language element.

Hi,
I don't think the sorting field is good for this or needed.

Anyways, a solution is needed, of course - but I am not sure if this will make it into 4.0.
Greets, Sebastian

It will not make it for 4.0, but I confirm the issue. Its not a mistake, we just didn't find time to implement this.

attached an extension (tested on version 4.1.5) + TV patch (tested with TV version 1.3.1) that fixes the cut/paste and copy/paste of contents with translations.

Related to http://bugs.typo3.org/view.php?id=10552

I tested Philippe's extenstions in two of my installations:
TYPO3 4.1.7 / TV 1.3.4 global
TYPO3 4.2.10 / TV 1.3.7 local

I tested: copy; move; reference>create local copy
all those actions now preserve the localizations.

GJ Philippe, thank you!
ian

Typo3 4.2.6 / no TV

I only install the translation extension and copy a localized content element. The content elements are copied both twice. See screenshots ...

looks good. Now we need core patch (i will take care for TV)

0002314_v2.patch should resolve the problems...

0002314.patch had issues since the placeholder-records for moved localizations weren't localized themselfes (which cause some renderings-issues within the list-module)

Hi,

I tested the patch / extension (0002314_v2.patch and T3X_klee_translation-0_1_2-z-200812051716.t3x) with TYPO3 4.2.9 and it works.

The extension T3X_klee_tv_move_patch-0_1_0-z-200812051717.t3x seems not to be necessary. If you also use this extension, the main element will be copied twice.

Without T3X_klee_translation-0_1_2-z-200812051716.t3x the translated element will not be copied.

Regards, Nils.

Hi there!

I witnessed some strange behavior of the extension:
(might be relevant to the patch, too)

When copying elements within "web->list" module, everything works as expected.

But when copying elements in "web->page" module, the copied elements have lost their translation relations and localisation settings, they all appear in the default language column now.

Kind regards, markus

@Markus: which files do you have installed? Just the extension or also a patch?

@nils: Just the extension: T3X_klee_translation-0_1_2-z-200812051716.t3x

@Markus: I needed also the 0002314_v2.patch like I've written a few notes above.

OK, that might cause the problem...
the issue is with a TYPO3 v4.1.7 here.

Hi there again.

I still encounter that weird behavior that copied content elements with translations somehow loose their relations...

Tested in TYPO3 v4.1.7 and v4.2.9, patch 2314_v2 and T3X_klee_translation-0_1_2-z-200812051716.t3x installed.

Here are the steps for reproduction:
1. apply patch 2314_v2
2. install T3X_klee_translation-0_1_2-z-200812051716.t3x
3. create test content with translations
4. now "web->page" copy only the element of the default language
and then "paste after"
Result: all elements get copied, but loose their relations.

The only way which succeeds in copying an element invcluding relations is within list module, table "page content" and then insertion via the table "head".

Ok, but when this new content element has to be moved somehow, it will still loose all its relations, eventually.

@Markus: is you destination page available in all languages?
Do you use TemplaVoila or traditional pages?

I use TV.

@Nils: I copy the elements on the same page - didn't tried to copy to other pages yet. No, I do not use TemplaVoila.

I've just sent a patch to the dev-list (it resolved a couple of related issues as well) - I'd be glad to get some feedback

@Tolleiv Nietsch: could you please write which files are needed for TYPO3 with TemplaVoila and which for a plain TYPO3 installation?

@Nils - this is no TemplaVoila issue - TemplaVoila just uses the t3lib_tcemain to perform copy/move/delete actions - please check the typo3.dev list and you'll find the Core-patch file - I didn't attach it to this issue because at the moment it resolves a couple of related issues at once (it not "Core-list ready" yet)

attached patch 0002314_v3.patch depends on changes from #14408- besides no other changes needed...

FYI: committed to trunk rev 6193