Step 1: Open a taxon page, for example at the link above (but this seems to affect any taxon page)
Step 2: Observe that under “Top identifier” it says “No identifications”, which is not the case. Wait for some minutes in case it is just a slow connection, but the identifiers still do not load.
Step 3: Click on the “Similar Species” tab.
Step 4: Observe that the “Similar Species” do not load, or take a long time (this appears to be more intermittent, as sometimes they load)
Step 5. Note that the Seasonality Chart is also not loading, although clicking on “History” does display the History Chart.
@tiwane Yes, I am (thanks for checking!), but I figured that since others can’t replicate it must be something at my end. It’s happening in both Firefox and Safari @konrad_k. I tried opening the browser console as @pisum suggested, but I don’t understand what I’m seeing there. It’s only a minor annoyance, so I wouldn’t worry too much about investigating it further. It will probably resolve itself with a browser update eventually.
If you want to just share a screenshot of the console, that would be helpful. I often don’t understand it myself, but it helps our engineers and others of the forum who can understand them better than I can.
I have similar on Firefox, it went away when I paused uBlock Origin and AdBlock Plus. It’s a new issue I haven’t run across before, I think in the last week.
Step 1: Access the iNaturalist website on any browser (it does not seem to make a difference whether I am logged in or not) and navigate to any taxon page regardless of rank.
Step 2: Observe that the top identifier for that taxon shows as “No Identifications”.
Step 3: Now navigate to any observation and expand the “Top Identifiers of [Observation Taxon]” section.
Step 4: Observe that the throbber animation continues perpetually and the top identifiers never display.
(N.B. I have now tried this on several browsers and on several different devices, both logged in and logged out.)
[Edited to add: see my next post below for some further observations.]
A couple of further observations I’ve made by repeatedly clicking into or refreshing taxon pages (on Firefox):
I am very occasionally (say, less than 5% of the time I click into or refresh a taxon page) able to get the top identifier to display correctly.
In the >95% of instances when the top identifier fails to display correctly, the seasonality chart is also stuck loading in perpetuity, and the buttons to see the sex, flowers and fruits, and leaves charts do not appear. You can see this in my first screenshot: note how only the buttons for the seasonality and history charts are visible. (However, in these instances, the history chart does work as it should.)
In the <5% of instances when the top identifier correctly displays, all the buttons for the charts appear and all the charts display as they normally should.
Interesting. I can’t replicate on PC (edge/chrome) or Android (chrome) at all…
I did have this issue a few times, tho. It always resolved itself by refreshing.
Does anything change when you apply a location filter? (just curious)
Just tried it. The top observer, last observation, and total observations all update, but the top identifier still doesn’t show and the seasonality chart still doesn’t load. Here are screenshots of before and after:
Interestingly, if I now click the history chart (i.e. after applying a location filter), it makes the buttons for the missing charts appear, but they (incorrectly) claim “No observations yet”:
It does look like the same issue, but I’d also noted in my initial post that the “top identifiers of [Observation Taxon]” section on observation pages isn’t working for me, being perpetually stuck on loading. (I didn’t think to make a separate report for that, since it seemed to me like another manifestation of the same problem.)
Is that best considered a separate issue? If so, is there an existing bug report for that, and if not, should I start one?
I would try enabling/disabling any extensions for testing and trying a VPN to see if that affects performance first and then using any results from those tests to determine whether this seems to be the same bug or different.
@deboas I think maybe you are in Brazil sometimes at least? You may want to take a look at the BR linked above as well and do some VPN testing or something to see if your report here is related.
