BUG: Suddenly can't search Cloud resources with Tags (Stop tinkering!)
I'm running v22.0.23 on Windows 10.
All of a sudden I can't search Cloud resources using mytags in Search. Did someone change something behind the scenes? I could search both Downloaded and Cloud resources using mytags until sometime yesterday. Now I get no results if I search a tag that is only on Cloud resources, and I only get downloaded resources if I search a tag that's on both downloaded and cloud resources.
It is very frustrating to have functionality changing even though I didn't change or update this installation of Logos. This is my main account. It seems as though someone is tinkering with things behind the scenes and it's impacting the search functionality. Please stop doing this. Please fix this for v22 because I am not ready to update this installation to v23.
Comments
-
Hi Kiyah--Sorry for the trouble here; at first glance, we aren't aware of anything that changed that would have caused a change/issue for you without you even updating your software. I just tried to reproduce and had no issues getting results for cloud resources with tags. So there's something more subtle happening here. Could you try this search again, and share the following:
- Your logs
- The specific search performed (including the query text) for which you expected cloud results
- A cloud resource or two that you had tagged, for which you were expecting results
Also, (sorry to state the obvious) please confirm that you are online and that you don't get a popup in the bottom right of your screen when you search telling you that there was an issue getting cloud results (if there's a network error or something like that, you would get a popup).
I'm also curious, thinking back to a previous issue on which we corresponded (I owe an update on this by the way; we made a fix for that previous issue that will get to you in an upcoming release), do these resources fall into the category of things you had downloaded, then recently removed, then re-built indexes, etc? Or are they more likely resources that have never been downloaded on your device?
0 -
Oh, might also be interesting if you could identify one of the cloud resources that you have tagged for which you expect results, and after searching with the tags filter on, also try filtering on that specific resource and perform the same search. If you're able, perform both of those searches, one after the other, before capturing the logs, and let us know the result.
0 -
-
Ah, yes, we did only just recently add cloud resources to the tags and ratings filter, and I failed to even consider this when reviewing your original post. So nothing 'changed' here in v22, but unfortunately (since you mention you aren't ready to upgrade to v23) the update we made to put cloud resources in that filter is in v23. So once you're able to update, this will work as you were expecting. Until then, hopefully you'll be okay using this workaround that you've found.
0 -
I'm also curious, thinking back to a previous issue on which we corresponded (I owe an update on this by the way; we made a fix for that previous issue that will get to you in an upcoming release), do these resources fall into the category of things you had downloaded, then recently removed, then re-built indexes, etc? Or are they more likely resources that have never been downloaded on your device?
I have since done a fresh install which fixed the other problem (I got tired of manually reindexing). I did another fresh install last night because I was removing v23 RC-2 and reinstalling v22. So all of my resources are freshly downloaded without me having to remove individual resources.
So this issue applies to all of the cloud resources. There seems to be a difference in how it's handling the "quick collections" versus the actual "mytag" selection option.
0 -
Ah, yes, we did only just recently add cloud resources to the tags and ratings filter, and I failed to even consider this when reviewing your original post. So nothing 'changed' here in v22, but unfortunately (since you mention you aren't ready to upgrade to v23) the update we made to put cloud resources in that filter is in v23. So once you're able to update, this will work as you were expecting. Until then, hopefully you'll be okay using this workaround that you've found.
Thanks. I had just noticed that this does work in v23 in my test installation. I tried v23 RC-2 in my main installation last night but it felt slower and clunkier so I went back to v22.
Yes, the workaround will work for me until I'm ready to update to v23.
0 -
> I tried v23 RC-2 in my main installation last night but it felt slower and clunkier
Kiyah--Could you provide more detail on this? Were there any specific areas of the app that felt slower and clunkier? Do you remember what you were doing when you noticed the sluggishness?
0 -
> I tried v23 RC-2 in my main installation last night but it felt slower and clunkier
Kiyah--Could you provide more detail on this? Were there any specific areas of the app that felt slower and clunkier? Do you remember what you were doing when you noticed the sluggishness?
It was when I was clicking to switch between tabs, and moving tabs. Also expanding and collapsing search results in the search window. So it was mostly interface speed with clicking on things.
I will say that I (accidentally) updated my main installation to v23 today from the default update channel. So now I'm on v23. It feels a lot better than it did last night. Maybe it did better with updating from v22 versus a fresh install. Not sure why but it feels a little closer to v22 now. But it was definitely slower last night. v22 was pretty fast for me so it was noticeably different. It seems to be doing okay today with the accidental update.
0