Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
As subissues of #2473989: Lack of dynamic language field / filter makes shipping core views hard to be both compatible with mono and multilingual we want to be able to see existing translations in the system.
Proposed resolution
- Show content in all translations by default
- Expose an filter to allow to filter by specific languages
- Still allow to filter by title/body as the admin/content view
Remaining tasks
User interface changes
API changes
Comment | File | Size | Author |
---|---|---|---|
#2 | make_a_node_translation_view-2474013-1.patch | 16.58 KB | pjbaert |
Comments
Comment #1
dawehner.
Comment #2
pjbaertI added a new view 'translated content' to the content page.
Comment #3
plachI'm not sure we actually want/need a separate view for translations. Assigning to Gabor to get some feedback.
Comment #4
Gábor HojtsyAs I said on #2473989: Lack of dynamic language field / filter makes shipping core views hard to be both compatible with mono and multilingual and/or related issues, if you look at the operations on the admin/content view (make sticky, unstick, promote, unpromote, publish, unpublish, etc) these relate to translations of an entity. There is no global publication/sticky/promoted status of an entity understood by Drupal. These are per translation. The same is true for most columns in the table on admin/content. They show publication status, change date, etc. of nodes. Again those are separate per translation. So not sure how is admin/content NOT a translation view and then why do we need another one?
Comment #5
Gábor HojtsyComment #6
Gábor HojtsyComment #18
smustgrave CreditAttribution: smustgrave at Mobomo commentedClosing out as outdated as there was no follow up from #4 when it ws moved to PNMI 7 years ago.
If you still feel this is an issue please reopen with an updated issue summary.