Feature #16437
closed
styles.content.get is limited to one language only at the same time
0%
Description
The default definition of "styles.content.get" is following:
styles.content.get {
table = tt_content
select.orderBy = sorting
select.where = colPos=0
select.languageField = sys_language_uid
}
Adding records with translations to a page this works only if users do not make the choice of "[ALL]" in the options menu.
The feature "select.languageField" is limiting the choice to one language only.
By a new definition like
"select.andWhere.dataWrap = hidden=0 AND (sys_language_uid=-1 OR sys_language_uid={TSFE:sys_language_uid})
#select.languageField = sys_language_uid
it's possible to query all required fields but the inactivated option "select.languageField" is important for the feature "config.sys_language_mode=content_fallback". If "select.languageField" is not set this and perhaps other features are not available.
Data-Rows with the choosen language "[All]" are stored with the language-Code "-1". Therefore the query has to accept two different language-Codes: "-1" and the userdefined one.
(issue imported from #M3987)
Updated by Martin Kutschker over 18 years ago
This has always been the case. Changing the setup like this may break existing installations. So I changed the severity to "feature".
It could be convenient to have a second set of styles.content.getXXX definitions that uses your definition. But IMHO anybody can change the TS he likes. There's no obligigation to use the default TS.
Updated by David Bruchmann over 18 years ago
The default "select.languageField" query of Typo3 is not correct.
This is a bug.
My Example serves only to show that build-in functionality of T3 may be corrupted by other definitions of "styles.content.get" as you mentioned.
Updated by Michael Stucki over 15 years ago
I agree that [ALL] should be selected by default. However, I agree with Masi that it can't be fixed easily. If e.g. we change tslib_cObj::getWhere() that it always selects the "language" '-1' (ALL) then it will most likely return more rows than currently, including duplicates (someone might add a record for ALL and one more for a particular language).
How should we deal with this?
Updated by Alexander Opitz about 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - TYPO3 Version set to 4.0
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.