Images from private repos are not accessible on frontend about wordpress-markdown-git HOT 2 CLOSED

Puuh, this was rather not so intuitive!

Everything is alright actually, the camo.blbla is just Github stuff added. The data-canonical-src tag tells you the original image. Basically the problem here is that you reference an image which needs authentication. Log out of Bitbucket and see if you can access the URL https://bitbucket.org/pacificdisastercenter/disasteraware-master-user-guide/raw/25d3aec045385c54b84ad90c88648cc9f75f3bba/images/1.2_figure_1.png. I can't let the plugin authenticate the URL for the image AFAIK.

Think I found a way to work around this in a series of experiments:

Don't take the image URL from the file itself, take it from the markdown on Bitbucket with right-click on the image itself and Save image address. It should look smth like https://bytebucket.org/nilsnolde/test-wp-plugin/raw/75cae613d140954349185292bdd5acd29a1a4ebe/img/IMG_0138.jpg?token=6d1d5454701e6426eb7dfb0009038358ae72f9f0. The important part being bytebucket.org and the token.

Now, I'm not sure how permanent that token is, but I'd figure it won't expire, since it's a static link. Of course Atlassian has a shit documentation for Bitbucket, which doesn't include that. And thanks to not being open source no way of knowing.

If you use that link instead in your markdown source code it will work. Do let me know if it did pls.

If, against all expectations, that token indeed has an expiry date and will invalidate at some point, the most sustainable option would be to have a separate public image repository or use a proper delivery service.

from wordpress-markdown-git.

Just released 1.0.2:
https://wordpress.org/plugins/documents-from-git/

I added a "Troubleshooting" section describing this as well.

Closing, but feel free to open if anything unclear remains.

from wordpress-markdown-git.