Bug #89249
closed
Changing language of a translated record to default should set l10n_parent to 0
Added by Anonymous over 4 years ago.
Updated about 4 years ago.
Category:
Language Manager (backend)
Description
Way to reproduce:
Create a record.
Translate it to a translation-language.
Edit the translated record and set its language back to default language.
The frontend then overlays the original record with its translation (which exist in the same language) and shows the translated record anyway.
Reason is that the l10n_parent is still in the database.
I tested this with news and tt_content records but expect to reproduce this with all kind of records as long they follow the default translation behaviour.
Don't know about pages... ?
I think the solution for this is: When a record is set to the default language the l10n_parent field schould be cleared or set to "0" in the database.
- Status changed from New to Needs Feedback
Is this issue present on 10.4.0-dev?
I tried with the following test
Prerequisites¶
1) TYPO3 with two languages (ITA (default) and ENG (ID=1) )
2) On the Sites configuration, select for ENG [fallbackType] = strict
Test procedure¶
1) Create a page in ITA called "test" and translate it in ENG ("test-eng")
2) Create in it a content element (e.g. an Headline element) "Test element" in default language
3) Translate it using translate (connected) mode ("Test element in ENG")
4) Save
Results:¶
- on frontend, the ITA version of the page contains "Test element"
- on frontend, the ENG version of the page contains "Test element in ENG"
5) Edit the translated content
6) Set its language to default[0]
7) Save
Result¶
- in backend, page module - languages view the "default" (ITA) column contains both element
- "Test element in ENG" still has [l10n_parent] field filled with the ID of "Test element" , but it is not visible on the backend
- on frontend, the ITA version of the page contains both "Test element" and "Test element in ENG"
- on frontend, the ENG version of the page is empty
Am I missing something? Is a different test necessary?
Can not reproduce this with current 9.5.15 - so this can be closed.
- Status changed from Needs Feedback to Closed
@Tobias Gaertner
Thank you for your feedback, closing it.
If you think that this is the wrong decision or experience the issue again or you think that there is still something to be done here, please reopen it or ping me and I'll do it.
Thanks.
Also available in: Atom
PDF
Updated by