Problem/Motivation
The Select translation filter currently only works when the Views base table is node_field_data.
Projects using the Group module (e.g. base tables groups_field_data or group_content_field_data) cannot use the filter, even though Group entities are translatable in the same way as nodes.
This prevents site builders from applying consistent translation fallback behaviour across nodes and groups.
Steps to reproduce
1. Enable Group module (tested with 3.3.5).
2. Create a View with base table Group (or Group content).
3. Try to add a filter: Select translation is not available in the filter list.
Proposed resolution
• Extend the filter plugin to work generically with any translatable content entity type, not only nodes.
• Dynamically resolve base table and entity keys (id, langcode, default_langcode, status) from the entity type definition, instead of hardcoding nid and node_field_data.
• Add hook_views_data_alter() to register the select_translation_filter for additional base tables:
• groups_field_data (Group entities)
• group_content_field_data (optional, Group content entities).
• This allows the existing filter to appear in Views for Groups and apply the same translation fallback logic.
Remaining tasks
• Review patch implementation for coding standards and backwards compatibility.
• Add automated test coverage for Groups (similar to existing Node test coverage).
• Update README / documentation to mention Group entity support.
User interface changes
• The Select translation filter will now appear as an available filter in Views where the base entity is Group or Group content.
• No other UI changes.
API changes
• None. The plugin ID remains the same (select_translation_filter).
• Only internal logic is extended to support more entity types.
Data model changes
• None.