Closed myrmoteras closed 4 years ago
I assume these are treatment UUIDs? At least they resolve in that role ... well, here's what I find:
Am I looking in the wrong place?
I thought you need to article UUIDs? At least I copied them from the article lsid. But they should be unique and not resolve to something?!
When you search on google, the you get the article https://www.google.com/search?q=CE6EFFC6FF8EFFFE6D07FFDBFFFE8717&rlz=1C1CHBD_enFR843FR843&oq=CE6EFFC6FF8EFFFE6D07FFDBFFFE8717&aqs=chrome..69i57.500j0j7&sourceid=chrome&ie=UTF-8
one more FF81FFE8FF87FFC46F20FF824F23FFCA
I thought you need to article UUIDs? At least I copied them from the article lsid. But they should be unique and not resolve to something?!
If they are not unique, that would definitely bother me ... what could be is that the images have been repaired long ago, but the broken predecessors are still out there ... I'll run the cleanup routine on the articles.
When you search on google, the you get the article https://www.google.com/search?q=CE6EFFC6FF8EFFFE6D07FFDBFFFE8717&rlz=1C1CHBD_enFR843FR843&oq=CE6EFFC6FF8EFFFE6D07FFDBFFFE8717&aqs=chrome..69i57.500j0j7&sourceid=chrome&ie=UTF-8
Clicked each of the three links I get in the result, and the images are fine ...
Cleaned up now ... these were just figure depositions that had been replaced by the repair routine long ago and were no longer linked to from the articles or treatments.
@gsautter here are some rare broken images
FF83FFE25D60FFC5FFC4D42D7D5BFF8C FFFE7B44331EA94AFFBEFFCF95697D0F CE6EFFC6FF8EFFFE6D07FFDBFFFE8717 405AFFE1FFED3C59FF80FFB0FFEAE73E