In i18n taxonomies might have languages. If you run a multilingual site, some forums might limit their post language to a single language.
In our cases: we have multilanguage forums (where language selection is open to the user) and we have forums with assigned languages.
If a user now posts a topic to a certain (single language) forum - language settings should get enforced. I'd also recommend to preselect the correct language for a given forum (/node/add/forum/xxx) - which should really be a feature of advanced_forum.
I'd also optionally i'd like to see forum selection disabled on the add page (will add configurable feature request later) which should also result in language selection disable (if fixed per forum).
In case of forum change we might synchronize language settings using ajax - based on forum term language information.
I'd like to see some other opinions to finally improve some forum functionality for multilanguage setups.
What do you think?
Comment | File | Size | Author |
---|---|---|---|
#4 | advanced_forum-i18n_support.patch | 1.55 KB | liquidcms |
Comments
Comment #1
MichelleDisabling forum selection already has an issue so please don't file a new one.
As to all the language stuff, if someone writes patches and someone tests them (preferably not the same someone), I'd be willing to commit them, but it's not something that I, personally, will write.
Michelle
Comment #2
MichelleBeen a couple months and no further interest.
Michelle
Comment #3
liquidcms CreditAttribution: liquidcms commentedthis patch adds some i18n support to AF.
#1 - it uses localized terms for the Forum listing page
#2 - i couldn't sort out best way to set the title of the actual forum page to the name of the localized term so i simply changed the title of the ctools Page context for %forum:name to use localized terms. to use this simply enable the Forum override in Panels and then set Page title to %forum:name
which gives me this:
http://screencast.com/t/KBlYrsLGFQ4
http://screencast.com/t/kvuLZuFwGNKX
Comment #4
liquidcms CreditAttribution: liquidcms commentedoops.. and the patch
Comment #5
MasterChief CreditAttribution: MasterChief commentedHi liquidcms, just a question did you try to translate containers with your patch ?
Comment #6
MasterChief CreditAttribution: MasterChief commentedHi liquidcms,
your patch doesn't apply against 6.x-2.x-dev version of advanced forum, i checked my core-ovverides.inc file, and the code you are replacing doesn't exist :(
Comment #7
liquidcms CreditAttribution: liquidcms commentedahhh. sorry; didn't notice version for this post.. its 2012.. so of course my patch is against D7.. :)
will change ver here to match
Comment #8
troky CreditAttribution: troky commentedPatch is already committed to 7.x. Check #1617840: Forum listing doesn't show translated terms.
Comment #9
liquidcms CreditAttribution: liquidcms commentedahh.. ok.. sorry.. i guess i x-posted the patch to confuse everyone.. and ended up just confusing myself.
so i guess this thread would now be about back-porting that patch?