-
Notifications
You must be signed in to change notification settings - Fork 30
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
Taxa 'Group' in Explore Your Area is showing incorrect taxa #604
Comments
Specifically, this exact URL + clicking on [Ferns and allies] reproduces the exact behaviour in the screenshot above: https://biocache.ala.org.au/explore/your-area#-35.3515|149.2330|12|ALL_SPECIES Doing this alters the URL to https://biocache.ala.org.au/explore/your-area#-35.3515|149.2330|12|Ferns%20and%20allies but refreshing or browsing to this new URL shows a map with no dots and a perpetual "loading data..." message in the table. |
Other than interacting with the page and looking at results, this URL can be used for testing https://biocache-test.ala.org.au/explore/your-area#-35.3515|149.2330|12|Ferns%20and%20allies. Prod shows "loading..." and does not update, test does update and selects the expected "Ferns and allies" in the left hand side list. |
I'm getting the page stuck on "loading data" for all of the larger groups (1000+), such as All species, Animals, Plants. Other than this, explore your area is working well |
Retest has passed, functioning well for all groups, including those larger groups |
Deployed in version 7.1.0. |
The [Ferns and allies] Group in Explore Your Area is showing kangaroos and birds and frogs as well as plants. This is also happening on biocache-test.
Other Groups appear to be filtering correctly.
Steps to reproduce the issue:
Add on steps
5. Click on a different Group to check search results
6. Allow time for the results to fully load
7. Click on [Ferns and allies] again and see if results are still incorrect
It's happening for me on Chrome, Firefox and Safari
cc @timhicks-ala
The text was updated successfully, but these errors were encountered: