Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website): Website
App version number, if a mobile app issue (shown under Settings or About): -
Browser, if a website issue (Firefox, Chrome, etc) : Firefox
it appears also impossible to vote on âBased on the evidence, can the Community Taxon still be confirmed or improved?â
something does seem bugged here.
@naufalurfi, it appears that you voted âyesâ on âcan the Community Taxon still be confirmed or improved?â Can you retract that vote? That might solve the issue.
I tried voting no to counteract it, and my vote wouldnât âstickâ at all. Nor would voting yes. So i do think thereâs additional bugginess here or something.
I actually thought voting it would solve the problem, but when i did it didnt register at first. Now instead it doesnt do anything when i clicked to retract the vote.
I added an agreeing ID, and then clicked and unclicked âorganism is wildâ - now it is research grade at family level somehow?? I also tried to add an âID can be improvedâ vote and could not.
Edit to add: I notice both of these are uploaded via Flickr, in case that has anything to do with it.
Yes, itâs related to the tags. We instituted a tag check on upload to prevent this from happening about two weeks after this observation was posted. Iâll have to play around with it on our test server to see exactly whatâs causing the issue and then reach out to the observer to see if they want to remove any of their tags.
I think I may have some observations with a similar plethora of tags from Flickr imports. The taxonomy tags look like machine-readable tags that were added on Flickr to facilitate import for some other sites, e.g. https://eol.org/.
Basically thereâs an overall character limit to the tags section of an observation. If the limit is breached, then the observation canât completely save.
At the time this was uploaded we werenât running checks to see if the limit was breached because I donât think we expected it to be breached. We added a check on upload about two weeks after this observation was uploaded.
