Cannot open About page for Helodium blandovii or its varieties from the Taxonomy tab

Bug Reports
1

Platform: Desktop

Browser, if a website issue: Chrome

URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/taxa/157555-Helodium

https://www.inaturalist.org/taxa/157560-Helodium-blandovii

Description of problem: I am unable to open the About page for Helodium blandovii from the Taxonomy tab for Helodium. I am also unable to open the About pages for any of the varieties of Helodium blandovii from the About page for Helodium blandovii. All other pages work fine (as best I can tell), including Helodium paludosum. I also tested this with the same result on the browser version on Google for Android and Safari on iPhone. It is possible to open the page for Helodium blandovii and all its varieties on the Android app.

Step 1: Open https://www.inaturalist.org/taxa/157555-Helodium or https://www.inaturalist.org/taxa/157560-Helodium-blandovii

Step 2: Navigate to Taxonomy tab.

Step 3: Click on Helodium blandovii or Helodium blandovii varieties, respectively.

Step 4: About pages for clicked taxon do not open.

Unrelated note: the correct orthographic variant of Helodium blandovii is as written. I was in the middle of changing to this from Helodium blandowii when I found this bug. It does not appear to be related to the name change, and was present before it (I was hoping changing the name would force a re-index and fix it, but it did not). The varieties still need to be swapped to fix the species epithet.

2

the error returned from the API is:
{"status":"500","errors":[{"errorCode":"500","message":"Invalid response for status code 200: results/0/conservation_statuses/0/place/name: must be string"}]}

seems like it could be related to this:

image
image866×957 221 KB

if so, it seems like something that could be fixed by fixing the data, but it probably should be handled more gracefully on the page, too. it may be worth holding off on any attempted data fixes to let iNat developers have a chance to debug the issue.

3

Thanks, taking a look.