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

Pnp TaxonomyPicker suggestion/match does not work as expected #604

Closed
geltapatio opened this issue Jul 8, 2020 · 6 comments
Closed

Pnp TaxonomyPicker suggestion/match does not work as expected #604

geltapatio opened this issue Jul 8, 2020 · 6 comments
Labels
status:fixed-next-drop Issue will be fixed in upcoming release. type:bug
Milestone

Comments

@geltapatio
Copy link
Contributor

geltapatio commented Jul 8, 2020

Category

[ ] Enhancement

[X ] Bug

[ ] Question

[ 1.9.0 ]

Expected / Desired Behavior / Question

you can find any term, which is part of the configurated taxonomy hierarchy
if the user searches for a subordinate term suggestion/match will display it.

Observed Behavior

The suggestion/match of TaxonomyPicker only finds main terms. The subterms could not be found.

Steps to Reproduce

Example

if you search with "Kap" suggestion/match will display "Kapitel1"
if you search with "Th" suggestion/match will not display results
if you search with "Ab" suggestion/match will not display results
[] Kapitel1
--- [] Thema1
--- --- [] Ablauf1
--- --- [] Ablauf2
--- --- [] Ablauf3
--- --- [] Ablauf4

bidl1_tems

Current Version

Main Term (Kapitel1) was found
bild2_KapitelOK

subordinates (Ablauf1, Ablauf1_3ToDelete, Ablauf2, Ablauf3, Ablauf4) could not be found.
bild3_AblaufNOK

subordinate (Thema1) could not be found
bild3_ThemaNOK

Thanks!
Luis Miguel Gamiz Espinosa

@ghost
Copy link

ghost commented Jul 8, 2020

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@ghost ghost added the Needs: Triage 🔍 label Jul 8, 2020
@geltapatio
Copy link
Contributor Author

geltapatio commented Jul 10, 2020

I already fixed it and created a pull request Pull Requestt

@AJIXuMuK AJIXuMuK added status:fixed-next-drop Issue will be fixed in upcoming release. type:bug and removed Needs: Triage 🔍 labels Jul 12, 2020
@AJIXuMuK AJIXuMuK added this to the 1.20.0 milestone Jul 12, 2020
@AJIXuMuK
Copy link
Collaborator

@geltapatio - thank you for reporting and fixing the issues.

The PR has been merged and will be available in the next release.

In a meanwhile please test the functionality in beta version.

@TheThor59
Copy link

Hello @AJIXuMuK

could we mark #624 and #629 as duplicate of this ticket as a fix has been impremented on beta ?
Alors I've just made a pull request to fix the new correction as there is an issue when using empty GUID, this is linked to this point.

Thanks

@limcysam
Copy link

Caan you please let me know when will the next version with the fix be released?

@AJIXuMuK
Copy link
Collaborator

@limcysam - we're planning to release the next version in the next two weeks or so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:fixed-next-drop Issue will be fixed in upcoming release. type:bug
Projects
None yet
Development

No branches or pull requests

4 participants