Bug #14578
closed
DB record disappears when language != default and Localization-View enabled
Added by old_beryllium over 19 years ago.
Updated about 6 years ago.
Description
If the language of a content-element is different from the default language-uid (0), the element is not displayed in the Localization-view if it doesn't have its "Transl. Orig." set.
To reproduce:
Create a page, create its translation. Go to List-view, enable Localization-view. Create a database-record (e.g. a news-item). The item is displayed. Now, click the Edit-icon of the item and select another language for it. The item is now vanished. You can view it again by disabling Localization-view though.
Possible workaround:
In file typo3/class.db_list_extra.inc, line 321:
Changte the $addWhere to:
$addWhere.=' AND ('.$TCA[$table]['ctrl']['languageField'].'<=0 OR
'.$TCA[$table]['ctrl']['transOrigPointerField'].'=0)';
This way, items with a different language, but without a 'parent' item are still shown. Problem with this solution is that the language isn't shown behind those items (normally it states 'Default' or 'All languages').
(issue imported from #M845)
Ow, btw, I stated version 3.8.0-dev, but it probably also applies to versions 3.7+, as Localization was added there.
I used the nightly snapshot of 2005-02-02.
I would say, that this is no bug but a feature. g
The possible workaround does not really fix the "problem" because records whose parent was deleted are stil disappearing from localized lists. (there transOrigPointerFields are not 0)
but I agree with you, that this is neither logical nor userfriendly. At the moment I have no solution for this. Something with two seperate lists should be possible - one for the localized news and one for the non-localized ones.
I'll take a look a it.
something different:
you wrote: Problem with this solution is that the language isn't shown behind those items (normally it states 'Default' or 'All languages').
-> this is fixed in TYPO3 3.8.0beta2.1 (see bug 920)
I have also an project where the translation-process of articles not always could use the default language. New articles are added in multiple languages and than these articles would be translated.
IMHO a true fix would it be, if:
- articles in all languages are listed if there are not translated from other languages or the original article is deleted
- articles could be translated (this languages-flag-navigation-feature) not only from the default language. (i.e. a german article is added and could be translated in all other languages, like an article in default language)
I would call it an more flexible localization of articles. At the moment you must choose a default language and must all articles have available in this default language at first, befor any translation could be done.
This is fixed at least since 4.2:
If localization-view is enabled in Web->List, a element will still be displayed in the list, even if "Transl. Orig" isn't set for it (tested with tt_news & tt_content records).
- Status changed from Resolved to Closed
Also available in: Atom
PDF