Make it multilingual, to work with i18n
agrigor1 - January 8, 2009 - 02:24
| Project: | Announcements |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Description
For multilingual sites the translation of an announcement should not lead to the creation of a new announcement that is visible as a separate new announcement. This is what it happens now and makes your module inappropriate for multilingual sites.
Please correct me if I am wrong (in such a case please instruct me how to have the described functionality)
I use drupal 6.8 just in case this is helpful.
#1
This is to be solved in your view settings. i18n supports view integration (make sure it is enabled). This makes it possible to use "Contenttranslation" as a filter.
Does this solve the problem?
Not using this module but thinking about it. Therefore I might have understood your request incorrect.
#2
I don't have any multilingual sites, so I can't test anything. It is my understanding that i18n will create a new node - and you really want that. Perhaps I need to look at my queries to see if I need to do anything more for i18n.
#3
My queries include db_rewrite_sql which should give i18n the opportunity to limit the language. Have you opened an issue with i18n? Their developer docs are terrible to non-existent.
#4
#5
You need to activate multilanguage through the workflow settings of this content-type at
admin/content/node-type/announcements
However I would still suggest to change the weights for the Annoucment-form, so the Language-Swichter doesn't float around in the middle of the form.
#6
Thanks, Niels. What does this do to sites that don't translate?
#7
Nothing.
The Translation-module injects a little language-selector-form-field via hook_form_alter, they use a negative weight to float on top. In the annoucement.module, negative weights are used as well, so the language-selector-form-field just floats around somewhere.
I changed the current form to use positive values (heavier), now the language-selector-form-field is on top like when you create a page.
#8
This ends up putting the dates and abstract below the body -- not good.
#9
I did the best I can.
Committed to both branches.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.