Bug #8522
Foreign tables shouldn't have a localization confusion
| Status: | Accepted | Start date: | 2010-06-28 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Dirk Wildt | % Done: | 0% |
|
| Category: | Localisation | Spent time: | - | |
| Target version: | 4.7.0 | |||
| Votes: | 0 |
Description
If foreign tables have a localization confusion, there will be a bug.
Localization confusion means:- Some foreign tables has localized fields, some others not.
- You can't use tables with and without localization fields in a query
- Foreign tables without localization fields have to extended with localization fields.
History
Updated by Dirk Wildt almost 3 years ago
- Status changed from New to Accepted
Updated by Dirk Wildt almost 3 years ago
- Target version set to 3.4.1
Updated by Dirk Wildt almost 3 years ago
- Target version deleted (
3.4.1)
Updated by Lorenz Ulrich over 2 years ago
Does my problem have anything to do with line 376 in pi1/class.tx_browser_pi1_views.php?
I was trying to display non-localized records from tt_address on a localized page. Just displaying all the records worked fine in default and in additional language. But filtering didn't work due to an empty AND statement at the end of the SQL query. I tracked it down to
$andWhere = $this->pObj->objLocalize->localizationFields_where($table);
$where = $where.' AND '.$andWhere;
Commenting it out made the extension work properly.
Updated by Dirk Wildt over 2 years ago
Dear Lorenz,
Thanks for your workaround.
Kind regrads
Dirk
Updated by Dirk Wildt about 2 years ago
- Target version set to 4.7.0
Updated by Lorenz Ulrich about 2 years ago
I'm still not entirely sure that my problem is the some as described above:
I have a localized page in German, French and Italian. On this page I have a non-localized database containing information about books, DVDs etc. So if a book is in German language, its title and description is in German, even if it's displayed on the italian version of the website.
But: The filter labels (true mm-relations) must be localized. Therefore I use the "language overlay" feature.
By default, browser complains that there is no field l18n_parent in my table. Why should there be one in my case?
Uncommenting the
$andWhere = $this->pObj->objLocalize->localizationFields_where($table);
stuff makes it work.
Updated by Lorenz Ulrich 11 months ago
Obviously this issue is already fixed. The lines that were commented (as stated above) are now uncommented and localization works out-of-the-box.
Updated by Lorenz Ulrich 3 months ago
You can close this issue.