Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/): The page is just blank and white, aside from the usual things at the top (iNat home page, explore, your observations, community, etc.), so a screenshot would be, in my opinion, boring. I do not include it because it is just a blank white page.
Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.): I understand that the Gerald page takes a long time to load, but I’ve never seen anything quite like this. The loader twirls about, then disappears and I’m left with a blank white page. Not even the Search Mole pops up!
I have that issue too, I think someone else on the forum said that clearing your cache should help? I haven’t tried that myself just because clearing my cache on my laptop messes up the way I have stuff set up, but clearing the cache may help.
This is probably the reason for the blank page. The traceback will lead someone with access to a debug version of app and/or the sources to the culprit. Some part of the loading process assumes an existing “user” property which is not available at this point.
Oh no, have Gerald and his associated website stress test finally met their end? Maybe someone can export a PDF of the observation and then it can be retired from edits. Though i still don’t feel like Gerald had nearly enough fields filled out for him.
i could probably fix the observation, but the question is: should i?
the observation loads fine if you view it in the website while not logged in. the main difference betwen logged in and not logged in that i can see is that you don’t see who faved an observation when you’re not logged in, and i assume that’s the part that is causing the page to fail to load when you’re logged in. that’s probably something that should be fixed, but it’s such a minor bug, a relatively small percentage of observations have any faves, let alone get faved by users who subsequently delete their observations.
the observation probably just needs to be reindexed. if reports that the Next app will open the observation just fine are true, then the easiest way to trigger the observation to be reindexed is probably just to make any update to the observation via iNat Next. (depending on what kind of chance you make though, that may end up subscribing you to the observation, if you’ve never subscribed to it before, and you might have to take an extra step to unsubscribe.)
otherwise, someone would probably have to make an update to the observation via the API. although i could do it, it’s not clear to me that i should try fix it without iNat staff having a chance to look at it.
everyone should still be able to view the observation simply by loading it in a private browsing sesssion where they’re not logged in.
