Bug #70460

Categories for translated pages/categories get lost

Added by Sascha Löffler over 4 years ago. Updated over 2 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Categorization API
Target version:
-
Start date:
2015-10-07
Due date:
% Done:

0%

TYPO3 Version:
7
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I will try to explain the issue.

I have one category in the default language.
Now i translate the category title into the second language.

then i have a page in both languages and assign the category to the page. When i save it, the page gets assigned to the category in the default language. (visible at the items tab for the category)

but no page is assigned to the translated category. If i add the page manually to the items in the translated category i get it to display with the attached typoscript.

But as soon as i save the default language again, the item in the translated category get removed again.

setup.txt View (1.38 KB) Sascha Löffler, 2015-10-07 11:45


Related issues

Related to TYPO3 Core - Bug #76629: Assigning translated categories doesn't work Closed 2016-06-14
Related to TYPO3 Core - Bug #68177: Wrong Categories on pages with pages_language_overlay Closed 2015-07-15
Related to TYPO3 Core - Bug #61923: Localization of elements and their categories in the backend Accepted 2014-09-27
Related to TYPO3 Core - Bug #80201: Categories in localized page Closed 2017-03-08

History

#1 Updated by Sascha Löffler over 4 years ago

  • Target version set to 7 LTS

I noticed yesterday that this behaviour does also give problems when using HMENU special = categories.
It does not return pages when the relation for translated categories get lost. (when using the uid of the english category)

#2 Updated by Markus Klein over 3 years ago

  • Target version deleted (7 LTS)

Seems to be a FormEngine bug.

#3 Updated by Markus Klein over 3 years ago

  • Status changed from New to Needs Feedback

Since the issue is already 10 month old. Has this by chance been fixed already?

#4 Updated by Riccardo De Contardi over 3 years ago

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!

#5 Updated by Tom Warwick over 3 years ago

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

#6 Updated by Riccardo De Contardi about 3 years ago

  • Status changed from Needs Feedback to New

#7 Updated by Mona Muzaffar over 2 years ago

  • Related to Bug #80201: Categories in localized page added

#8 Updated by Riccardo De Contardi over 2 years ago

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.

#9 Updated by Jo Hasenau over 2 years ago

  • Status changed from New to Needs Feedback

Just tested the described behaviour exactly the same way and IMHO the behaviour is as expected:

You are not supposed to assign categories to pages_language_overlay but to pages only.
This is why there is no Category tab when you edit the record of the translated page.

Relations are connected to the original language only and should then get the proper translation when the overlay is done.
So fetching the translations directly is not the way it's supposed to be done.
Same goes for connections from "the other side" by editing the category translation and assigning it to pages_language_overlay, which is not supposed to be done either.

#10 Updated by Riccardo De Contardi over 2 years ago

  • Status changed from Needs Feedback to New

Also available in: Atom PDF