- π³πΏNew Zealand quietone
Forum is approved for removal. See #1898812: [policy] Deprecate forum module for removal in Drupal 11 β
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project β and the Extensions approved for removal β policies.
It will be moved to the contributed extension β once the Drupal 11 branch is open.
- π§πͺBelgium ludo.r Brussels
This patch should solve the problem.
There might be more underlying issues to solve but it will get the translated titles to be displayed. - Status changed to Active
about 1 year ago 12:52pm 4 April 2024 - π©πͺGermany Anybody Porta Westfalica
Moved to Forum project, as the issue still exists!
- Open on Drupal.org βCore: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - Status changed to Needs review
about 1 year ago 1:36pm 4 April 2024 - Open on Drupal.org βCore: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass Patch #15 aka MR works fine and fixes the forum translation as expected
- Status changed to Needs work
about 1 year ago 8:07pm 5 April 2024 - π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
Code looks good, would be good to add tests for this as it feels like important functionality
- π©πͺGermany Anybody Porta Westfalica
Forum breadcrumbs still contain untranslated text (from Taxonomy terms).
I didn't find any other issues yet.
- π«π·France erwangel
MR!3 worked for me on Drupal 10.4.7 + forum 1.0.2 and forum names (Taxonomy terms) appear in the right language.
However topic titles still appear in the original/posted language. This has for effect to user to loose his interface language. My use case is to have forum/taxonomy terms translated; forum nodes are not translated but author can chose the content language.
Let's say we have lang1 as default language and lang2 as second language code.
Whatever the interface language is, topics are listed as follows:
Forum title is displayed in the interface language (after applying the patch, now it works as expected)
Topic 1 published in default language has aliased url1: forum/the_topic_1_title
Topic 2 published in lang2 has aliased url2: lang2/forum/the_topic2_titleIf a user navigates the site with the default language and clicks on topic 2 title (url2) all his interface language will switch to the lang2.
Same if he uses lang 2 interface and he clicks on url1, his interface will switch to lang1.
This is because interface detection is done from url's lang_code which I think is the most used case.I think the correct display of topics listing should be:
If interface language is default (lang1)
Topic 1 published in default language has aliased url1: forum/the_topic_1_title
Topic 2 published in lang2 has unaliased url2: /node/nid2If interface language is lang2
Topic 1 published in default language has unaliased url1: /lang2/node/nid1
Topic 2 published in lang2 has aliased url2: /lang2 /forum/the_topic_2_title