You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the 4.74.0 release, the following feature was added:
Lock and unlock items matching your current search from the same menu you use for tagging them
However, filtering items by, let's say, tag:infuse and then selecting unlock from the tag icon in the search bar will show the user the following message:
Unlocked 0 Items
Even when there are locked items matching the search result.
As shown in the above, the search result of tag:infuse is:locked would no longer have matched the is:locked portion if the unlock update went through, but they remained locked.
The text was updated successfully, but these errors were encountered:
Trying to reproduce this I also discovered that tagging is also not working, so none of the "mass" options are working. And tagging doesn't show the info popup...
I'm on mobile, so can't check console for error messages.
duckmanBR
changed the title
Unable to Mass Lock / Unlock via filtered results
Unable to Mass Lock/Tag via filtered results
Oct 17, 2018
So looking a little further, looks like the problem is that the combo selection is not properly triggering a refresh.
For the tag, I need to manually refresh (or just be luck for DIM auto refresh) to see the changes.
For the lock, it's taking a little longer (maybe some delay on Bungie side since lock is trough API while tag is 100% DIM?), but 1-2 manual refreshes are needed for the items reflect the (un)lock action.
TL;DR: DIM is correctly applying the option selected, but something is delaying the user to see it done.
In the 4.74.0 release, the following feature was added:
However, filtering items by, let's say,
tag:infuse
and then selectingunlock
from the tag icon in the search bar will show the user the following message:Even when there are locked items matching the search result.
As shown in the above, the search result of
tag:infuse is:locked
would no longer have matched the is:locked portion if the unlock update went through, but they remained locked.The text was updated successfully, but these errors were encountered: