Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version filter doesn't appear to be working when searching #578

Closed
PeteDuncanson opened this issue Apr 30, 2020 · 6 comments · May be fixed by #641
Closed

Version filter doesn't appear to be working when searching #578

PeteDuncanson opened this issue Apr 30, 2020 · 6 comments · May be fixed by #641
Labels
community/up-for-grabs status/stale Marked as stale due to inactivity type/bug

Comments

@PeteDuncanson
Copy link

As mentioned in #577 if you search for https://our.umbraco.com/search?q=migrations and have the default "V8" target version selected next to the search box the results seem to be from all versions and not just for V8 as I would expect.

@nul800sebastiaan
Copy link
Member

Aha.. not sure why that wouldn't work on the main search, it looks like it only works for the docs, but it should of course work everywhere.

@umbrabot
Copy link

Hi @PeteDuncanson,

We're writing to let you know that we've added the Up For Grabs label to your issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.

For more information about issues and states, have a look at this blog post

Thanks muchly, from your friendly PR team bot :-)

@AaronSadlerUK
Copy link
Contributor

Submitted a PR: #641

@leekelleher
Copy link
Member

I'm not sure whether the bug I've encountered is the same as this one... or whether the PR #641 fix resolves it too.
So posting on here, rather than creating a new ticket.

In a nutshell, when I filter the package listing by "Version 8", my Contentment package isn't listed. But if I select "Any" version it is listed. 🤷

I originally thought it was an UmbPack issue, so I've posted in more humous detail on their repo: umbraco/UmbPack#62

The suggestion is that the "Version 8" filter is only showing packages that are associated with v8.0+ only. Where as my Contentment package is for v8.6+, so doesn't show. But interestingly does show if you manually tweak the querystring to be v8.6.

@KevinJump
Copy link
Contributor

Had a look I think its how the packages are indexed and searched.

the versions are indexed here :

var allVersions = new HashSet<string>();

but they are then only referenced in the filters, which goes back to the major version .

I think - the fix is to add the major versions (to the num_version version field) when indexing the package - then the filter can use that.

@umbrabot
Copy link

umbrabot commented Mar 1, 2022

Hiya @PeteDuncanson,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@umbrabot umbrabot added the status/stale Marked as stale due to inactivity label Mar 1, 2022
@umbrabot umbrabot closed this as completed Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community/up-for-grabs status/stale Marked as stale due to inactivity type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants