- Issue created by @szantog
The Views Autocomplete Filters module currently forces contextual filters to be applied during autocomplete searches, preventing users from searching across the entire dataset. This limitation occurs because the module doesn't properly handle cases where we want to temporarily ignore contextual filters during autocomplete operations.
<!--break-->The current implementation modifies the argument configuration:
$enable_arguments = $expose_options['autocomplete_contextual'] ?? FALSE;
// Force "Display all values" for arguments set and ignore "No Contextual
// filter present" settings unless indicated by 'autocomplete_contextual'.
$arguments = $display_handler->getOption('arguments');
if (!empty($arguments) && !$enable_arguments) {
foreach ($arguments as $k => $argument) {
$arguments[$k]['default_action'] = 'ignore';
}
$display_handler->setOption('arguments', $arguments);
}
This approach is problematic because it alters the wrong display handler's configuration. Like it says: When the filter value is NOT in the URL If I don't misunderstand something, this logic should operate when the filter value IS in the url.
Current Behavior: Autocomplete searches are restricted to the current contextual filter's subset of results, limiting the user's ability to find matching entries across the entire dataset.
Expected Behavior: Autocomplete should be able to search across the entire dataset when needed, regardless of active contextual filters.
Instead of modifying the display handler's configuration, we should set the contextual filter value directly the the Exception's wildcard value.
Active
2.0
Code