Platform: Website
Browser : Chrome
URLs: Any taxon page
Screenshots of what you are seeing:
Description of problem: Self-explanatory. After the taxon images are edited the banner stating the conservation status disappears.
Step 1: Go to any taxon page with an IUCN threatened status (VU or higher).
Step 2: Edit the taxon images in any way.
Step 3: The banner showing the conservation status should be gone.
I see it now:
It might just be a temporary glitch. Are there any pages where you find that the banner never comes back?
Seems to fix itself when refreshing. Not a serious issue obviously and I’m fine with not fixing it since this glitch has never, and will never, cause issues to anyone.
When I tested on H. fuenterroquensis it never came back, not sure why it’s behaving differently for you. Maybe I just didn’t wait long enough.
Possibly related…Under Status / Conservation Status, this information often doesn’t show the first time a page is loaded, but after reload there is information. Happens frequently. Chrome/Windows.
Platform: Website
Browser, Google Chrome
URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/taxa/93095-Achatinella-decipiens (any iNat species page with a threatened IUCN listing will work)
Screenshots of what you are seeing:
(2nd image is bugged, 1st is what it’s supposed to look like)
Description of problem: When you edit the taxon images, the conservation banner disappears. Notice the box with the flag saying the species is Critically Endangered disappears in the 2nd image.
Step 1: Go to any species with this threatened banner. I chose Achatinella decipiens
Step 2: Change the taxon images. You can add or remove 1 or more images and this will work.
Step 3: The conservation status banner image telling you the species is endangered/vulnerable/whatever is now gone. It comes back when you reload the page so it’s not a major issue but a weird issue nonetheless.
Extra screenshot:
Compare this screenshot with Screenshot #1 from the original post and you’ll see that it’s identical except for one thing that is missing.
Moved these to your existing bug report and I’ve made an issue for our engineers.
This should be fixed.
Confirmed fixed :)
