- πΊπ¦Ukraine id.conky UA, Lutsk
id.conky β made their first commit to this issueβs fork.
- Assigned to id.conky
- πΊπ¦Ukraine id.conky UA, Lutsk
id.conky β changed the visibility of the branch 3322625-add-ability-to to hidden.
- Merge request !85Issue #3322625: Added separate views filter definition to filter on thread members field. β (Merged) created by id.conky
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
11 months ago Waiting for branch to pass - πΊπ¦Ukraine id.conky UA, Lutsk
id.conky β changed the visibility of the branch 3322625-add-ability-to to active.
- Status changed to Needs review
11 months ago 12:51pm 27 January 2024 - πΊπ¦Ukraine id.conky UA, Lutsk
Added new filter definition to re-use "user_name" filter handler from core user module. This adds autocomplete to filter widget, so user can easily filter threads by it's members.
Also there is an alternative way to achieve similar behavior - apply core patch from https://www.drupal.org/project/drupal/issues/2429699 π Add Views EntityReference filter to be available for all entity reference fields Closed: duplicate and add next to your custom code:
/** * Implements hook_views_data_alter(). */ function your_module_views_data_alter(array &$data) { $data['private_message_thread__members']['members_target_id']['filter']['id'] = 'entity_reference'; }
Clear your cache and this will make members field looks like eneity reference with different settings.
If you experience duplicates - this is completely fine and normal behavior of SQL query. To fix so - enable aggregation and select "Group results together" in aggregation type settings.
- First commit to issue fork.
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
11 months ago Waiting for branch to pass -
artem_sylchuk β
committed 2c1860c1 on 3.0.x authored by
id.conky β
Issue #3322625: Add ability to views filter by username without...
-
artem_sylchuk β
committed 2c1860c1 on 3.0.x authored by
id.conky β
- Status changed to Fixed
11 months ago 1:09pm 27 January 2024 Automatically closed - issue fixed for 2 weeks with no activity.