TYPO3 Core

Hi I tried the following test with 7.6.10:

1) I have 2 languages, Italian (Default) and English (ID=1)
2) create a page in default language (Title: "Test")
2.1) translate it to english (Title: "Test ENG")
3) create a sysfolder in default language and translate it ("System Folder")
3.1) Inside system folder, create a category ("CAT1")
3.2) Translate the category ("CAT1 ENG")
4) Edit "Test" (default language), assign category "CAT1"
4.1) If I edit "Test ENG" there is no "category" tab.
5) "System Folder" > Edit "CAT1 ENG" > tab "Items" > add manually the "Test ENG" page, Save
5.1) The relation is saved

I then tried to
6) Edit the title of default language category CAT1
7) Edit the title of the page "Test"
8) Edit the title of the page "Test ENG"
9) Edit the page "Test" and unassign the category CAT1

Result: when editing "CAT1 ENG" the relation with "Test ENG" was never lost.

Am I missing something? Is there a different test to be performed? What do you mean exactly with

as soon as i save the default language again

?

Can you provide me a step-by-step procedure to reproduce the issue?

Thank you!

This is near identical to the issue I'm having, (re-post from forum.typo3.org)

Ive got a Multilanguage site running in English and Welsh.

Im using Categories to tag pages so that I can create an "A to Z" 

In the Default language (English) everything works fine. I tag a Page with a particular category and I then use the content element "Special Menus > Pages for selected categories" to generate a list of all pages tagged with a particular category.

I assumed, to do this for my alt language (Welsh) I would just need to create Categories with the alternative language and tag pages with both and English and Welsh categories. However, I cant see any categories in my alternative language when I browse to Page properties > Categories. I can only see categories setup in my Default language.If I change them back to my default language they appear straight away.

Is it the case that system categories can/should only exist in the default language?

I've seen several additional bugs on forge that have spawned from this, I assume this isn't going to get picked up?

Tom

I write here the description of #76629 to keep track of it:

Description

Assigning categories to pages doesn't save the translation of the category.

Steps to reproduce:
Create new page language
Create sys_folder for categories
Create new category "cat_01"
Create translation for category "cat_01" => "cat_01_de"

At this point the database has two categories with IDs '1' and '2' in table 'sys_category'

Create new page "category_index"
Assign "cat_01" to page "category_index"

At this point the database has only one entry in 'sys_category_record_mm' for the default language. But it should have both relations. One for 'cat_01' and one for 'cat_01_de' since this is just a translation.

Now, if you try to get the translated category via typoscript like this:

 table = sys_category
 select {
 languageField = sys_language_uid
 pidInList = 2
 join = sys_category_record_mm ON sys_category_record_mm.uid_local = sys_category.uid
 where.data = field:uid
 where.intval = 1
 where.wrap = sys_category_record_mm.uid_foreign=|
 orderBy = sys_category.sorting
 }

it works for the default language, but you get zero results for the translation.

As far as I can see on version 9 the following happens with two languages: ITA and ENG (ID=1)

1) Create a category in default language (CAT01_ITA) and translate it (CAT01_ENG); the two have different IDs
2) Create a page in default langauge (TEST ITA)
3) Assign to it the category CAT01_ITA
4) Translate the page (TEST ENG)

Results¶

the translated page has no category assigned; the category tree on TEST_ENG shows only the ones in the default language

If you repeat the test for a content element inside the page, and translate it (Translate "Connected" mode) then

- the category tree on the translated element shows only categories in default language
- the translated CE has the same category of the initial one in default language

Is this behavior intended?