What Wildbook are you working in? ACW
What is the entire URL out of the browser, exactly where the error occurred?
Encounter record here: https://africancarnivore.wildbook.org/encounters/encounter.jsp?number=4dd0c630-2c27-4947-8f10-99e91142e7b8
Sighting link: https://africancarnivore.wildbook.org/occurrence.jsp?number=Census_08-09_2.CHEETAH_Original_3_Jim&JaneLudlow
Can you describe what the issue is you’re experiencing?
When we click on the Sighting ID in the encounter record, we get a “no matching record in the database”. Can you tell me what I did wrong / how the Sighting could have gone missing?
I can confirm that occurrence Census_08-09_2.CHEETAH_Original_3_Jim&JaneLudlo does not exist in the acw database and that encounter 4dd0c630-2c27-4947-8f10-99e91142e7b8 thinks that it should be looking for it.
I also looked through the historical logs and don’t see any mention of Census_08-09_2.CHEETAH_Original_3_Jim&JaneLudlo, which I suspect I would see if someone were to have deleted it at some point.
I’ll escalate this to one of the other team members.
Hi @MarkF - it should be Jim&JaneLudlow - with the ‘w’ at the end, not Ludlo, just in case that matters?
Oh good catch! That did matter. That record DOES exist in our database. Now the question becomes why doesn’t https://africancarnivore.wildbook.org/occurrence.jsp?number=Census_08-09_2.CHEETAH_Original_3_Jim&JaneLudlow take us to it.
Thanks for the lead!
I picked up this issue as WB-1606 and have deployed a fix. It was the ampersand
in the sighting ID, this is a reserved character in URL’s. It’s now been encoded and
you should be able to visit the sightings with this character from the encounter page normally.
Ahh. Our mistake for including the special character. Sorry and thanks for the fix!