Multilanguage dependent listings are not supported at all
Eudaimonius - January 19, 2008 - 06:25
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | language system |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | patch (code needs review) |
Description
What are the steps required to reproduce the bug?
- add language
- set Language negotiation: Path prefix with language fallback.
- enable block: language switcher
- set content type/story/mutlilingual support: Enabled, with translation
- create story
- translate story to another language
- uncheck: promoted to front page (for translation only)
- view site's front page
- change language using the language switcher
What behavior were you expecting?
- display the translated version of the story
What happened instead?
- adress change to /xy/node (xy: language code)
- display original story, not the translated version
#1
The default frontpage shows all promoted nodes, irrespective of language. So when the translations are also promoted to the frontpage, they show up as well as their original stories.
According to the handbook page Paths and block visibility
This was written for 5.x, but should work as described for 6.x, so I dare say this can be marked as critical.
#2
This patch modifies node listings on default node path to show only nodes for the language selected.
#3
#4
I applied the patch and it works for nodes with a specific assigned language. However, this patch excludes language neutral nodes from the node listing on the front page.
#5
Thanks kdebaas. Corrected the error.
#6
#7
Yes, that worked for me.
#8
Well, this all comes down to admin/user expectations. Some might need language neutrals listed, some might not. People will need this for their taxonomy listings for their blog URLs, for their aggregator items, user listings, whatever, all these might need different setups. (Eg. list all blog entries but only list content in taxonomies with the current language). While this looks like a critical omission in Drupal 6, there are so many config options one would need to implement to make this work, and the multitude of missing multilanguage features already require you to use i18n or localizer module anyway, this is to be implemented in i18n/localizer in Drupal 6.
#9
Patch still applies, but, I'm not sure if the functionality is still needed, so, not testing.
Robin