#70460Categories for translated pages/categories get lost
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.
Reviews 1
Related issues 3
Files 1
History 17
-
Sascha Löffler commented and changed target version <span data-processor="relativetime" data-value="2015-10-09T09:55:58+00:00" > 10/09/15, 09:55 </span>
-
Markus Klein commented and changed target version <span data-processor="relativetime" data-value="2016-07-29T09:28:41+00:00" > 07/29/16, 09:28 </span>
Seems to be a FormEngine bug.
-
Markus Klein commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2016-07-29T09:33:33+00:00" > 07/29/16, 09:33 </span>Since the issue is already 10 month old. Has this by chance been fixed already?
-
Riccardo De Contardi commented <span data-processor="relativetime" data-value="2016-07-29T11:02:35+00:00" > 07/29/16, 11:02 </span>
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 savedI 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 CAT1Result: 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!
-
Tom Warwick commented <span data-processor="relativetime" data-value="2016-08-25T16:20:38+00:00" > 08/25/16, 16:20 </span>
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
-
Riccardo De Contardi changed status
Needs FeedbackNew <span data-processor="relativetime" data-value="2016-11-17T11:16:12+00:00" > 11/17/16, 11:16 </span> -
Mona Muzaffar changed Related to #80201 <span data-processor="relativetime" data-value="2017-04-29T23:55:17+00:00" > 04/29/17, 23:55 </span>
-
Riccardo De Contardi commented <span data-processor="relativetime" data-value="2017-05-14T21:04:36+00:00" > 05/14/17, 21:04 </span>
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. -
Jo Hasenau commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2017-06-04T01:21:24+00:00" > 06/04/17, 01:21 </span>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. -
Riccardo De Contardi changed status
Needs FeedbackNew <span data-processor="relativetime" data-value="2017-09-06T14:46:21+00:00" > 09/06/17, 14:46 </span> -
Riccardo De Contardi commented <span data-processor="relativetime" data-value="2020-03-20T15:42:54+00:00" > 03/20/20, 15:42 </span>
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 languageIs this behavior intended?
-
Christian Kuhn changed
Related to #76629<span data-processor="relativetime" data-value="2020-10-20T14:28:40+00:00" > 10/20/20, 14:28 </span> -
Christian Kuhn changed Duplicated by #76629 <span data-processor="relativetime" data-value="2020-10-20T14:28:43+00:00" > 10/20/20, 14:28 </span>
-
Christian Kuhn changed
Related to #80201<span data-processor="relativetime" data-value="2020-10-20T14:29:30+00:00" > 10/20/20, 14:29 </span> -
Christian Kuhn changed Duplicated by #80201 <span data-processor="relativetime" data-value="2020-10-20T14:29:41+00:00" > 10/20/20, 14:29 </span>
-
Christian Kuhn changed Related to #62727 <span data-processor="relativetime" data-value="2021-09-15T18:20:34+00:00" > 09/15/21, 18:20 </span>
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-10-16T14:19:54+00:00" > 10/16/26, 14:19 </span>I re-checked this on main (15.0.0-dev), once on DataHandler level with a functional test and once in the backend.
DataHandler
Setup: category “Cat” (uid 1) with a translation (uid 2), default page (uid 1) with a translation (uid 2).
Step sys_category_record_mmAssign category 1 to default page 1 -> 1 Assign translated category 2 to translated page 1 -> 1, 2 -> 2 Save the default page again (title changed, category 1 set) 1 -> 1, 2 -> 2 The relation of the translated page to the translated category is not removed when the default page is saved again, so the second symptom of the report (“the item in the translated category gets removed again”) does not reproduce.
Backend
The page translation now has a “Categories” tab. The category tree there only offers categories of the default language, a translated category (e.g. “Cat 1a” with its German translation) cannot be selected. Selecting a category therefore always relates the translated page to the default language category.
Conclusion
- Losing a manually added relation does not happen anymore.
- What remains is that translated records cannot be related to translated categories via the edit form. As described by Jo Hasenau in 2017 the relations are meant to be kept on the default language record and the category is translated via overlay. This is more a feature request (see #61923, #62727) than a bug.
Not checked: 13.4 and 14.3, and the frontend output (
HMENU special = categories,CONTENTwithsys_category_record_mmjoin).If this is still valid for you in v14, please open a new issue and provide information how to reproduce it. thanks
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)