This is fixed in 2.0.9.
if (value.toUpperCase().indexOf(filter) !== -1) {}
This patch causes issues on 10.3.*, due to the changes done in issue
https://www.drupal.org/project/drupal/issues/1349080
🐛
node_access filters out accessible nodes when node is left joined
Needs work
.
Is this patch still necessary?
Created a patch to check the status of account_field_split.
Temporary patch which can be used as long as we don't have a generic solution.
We've had the same issue here and moved to https://www.drupal.org/project/view_unpublished → . That module does exacly the same thing, and is more globally used than this one.
In my opinion, this is a very big usability improvement. Strange that this feature, which has low impact on the code, is not getting into the module.
When cloning nodes with translations, you don't want any incorrect translations being published.
Added a patch to use composer/installer ~2.0.
JurgenR → created an issue.
I've had a similar issue when using facets combined with an exposed filter, in combination with the https://www.drupal.org/project/views_ajax_history → module.
Forcing the pager back to 0, as done in the patch, fixed the issue.
I can't see any reasons why facets should not reset the pager when filtering, therefor this patch seems a good solution to handle those edge cases.
Updated patch against the latest rc1 release.
Updated patch against the latest rc1 release.