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

Wrong results in entry forms autocompletion #4010

Open
litvinovg opened this issue Sep 24, 2024 · 0 comments · May be fixed by vivo-project/Vitro#474
Open

Wrong results in entry forms autocompletion #4010

litvinovg opened this issue Sep 24, 2024 · 0 comments · May be fixed by vivo-project/Vitro#474
Assignees

Comments

@litvinovg
Copy link
Collaborator

Describe the bug

In entry forms autocompletion proposes wrong results (wrong type).
After having entered a text into the first (eg. person) field, autocompletion of subject area proposes persons instead of places.
Seems cache is not working correctly. Field type should have been used as a cache key, too.

To Reproduce
Steps to reproduce the behavior:

  1. Create a person with last name test and first name test
  2. Create a concept with name test
  3. Create one more person. Open person profile, go to teaching activities, open form to create advisees
  4. In Advisee last name field type test , notice that person is proposed
  5. Go to subject area field, type test, notice that the same person is proposed instead of a concept

Expected behavior
Autocomplete suggestions should only appear for the appropriate type.

Environment (please complete the following information):

  • OS: Linux
  • Browser Firefox
  • Tomcat version 9
  • VIVO version 1.15.1-SNAPSHOT
  • Apache Solr
@litvinovg litvinovg self-assigned this Sep 24, 2024
@litvinovg litvinovg linked a pull request Sep 24, 2024 that will close this issue
@litvinovg litvinovg linked a pull request Sep 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant