This ticket has been fixed as part of Wildbook 10.6.0. Seal Wildbook is currently on version 10.5.3, so the fix will appear on the next update cycle.
This ticket has been fixed as part of Wildbook 10.6.0. Seal Wildbook is currently on version 10.5.3, so the fix will appear on the next update cycle.