Closed NolanHill closed 3 years ago
I suspect this happens because the image is already "known" as an attachment by coyote; the hash for the source uri already exists in the coyote table, so any coyote API call is not made to attempt to insert a resource.
To fix this, I'll include "known" resources in the batch creation API call as well. Thanks for reporting this.
Fixed via https://github.com/coyote-team/coyote-wp/commit/51bf4e07011c1857a09834d4ac118cdc0f39e0fc; now always defaulting to https
for attachment URLs.