Filtering by Status=disabled also shows archived
See original GitHub issueDetailed steps causing the problem:
- have a list o caches imported from a GPX generated by GSAK based on geocaching.com data
- filter, select by status = disabled
Actual behavior after performing these steps:
disabled and archived caches are shown
Expected behavior after performing these steps:
only disabled caches to be shown.
Version of c:geo used:
2016-05-09
Is the problem reproducible for you?
Yes
System information:
Android 4.2.1
HW acceleration:disabled
Other comments and remarks:
If I filter by status=archived, only archived are shown.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Filter not showing (suddenly disappeared) on Elementor ...
Hi, We have a problem with an attribute filter that suddenly disappeared from the page. It worked fine for a couple of months...
Read more >Filtering the view by Owner displays disabled users
When I filter the view by Owner (ex. Active Contacts) and searching for specific user name, the search results display both enabled and...
Read more >Manage In-Place Archives in Exchange Server | Microsoft Learn
Go to Recipients > Mailboxes. · Select a mailbox. · In the details pane, under In-Place Archive, click Disable. Note: You can also...
Read more >product archive filters for attributes and off canvas doesnt show
hello guys I'm getting an issue and I don't find the answer in the topics. I can't get attributes filters on the filters...
Read more >Filtering Events - ZoneMinder Documentation - Read the Docs
The other things you can filter on are all fairly self explanatory, except perhaps for 'Archived' which you can use to include or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I added a PR that should fix the issue.
I would agree semantically that an archived cache is by default not active, thus not enabled, thus disabled. While the filter label “disabled, archived” would illustrate properly the current behaviour, from user and usage perspective, it is useful to filter by individual status meaning. That is: disabled: show only disabled. Arvhiced: show only archived.
If multiple filters are to be applied (future filter UI rework), or some other combination, each criteria should be designed to be atomic and , where applicable, mutually exclusive. It would leave much less room for errors.