Here's a test post.

by Paul , Monday, September 13, 2021, 09:23 (1168 days ago) @ Otony
edited by Paul, Tuesday, September 14, 2021, 07:47

I'm going to try three different ways to post the same image to see if we can get to the bottom of what's going on.

First, right below this text, is a random 1861 Colt that I grabbed a pic of off the 'net a while back. I used the "upload" button to the right of the post editing window to choose it from my hard drive and upload it. The forum system automatically inserts it into the appropriate brackets and tags and uses a modified URL in the process.

The image above this text uses the abbreviated (why is that such a long word?) URL as follows:

images/uploaded/20210913141141613f5c1dc4160.jpg

The forum system puts {img} in front of that URL and {/img} behind that URL (only it uses [ and ] instead of { and } ) to signify that there's an image that needs to be shown to the browser.

What I did last night was add https://sixshootercommunity.com/forum/ in front of the word "images" in the URL. This gives the complete URL that apparently Apple needs to recognize that that image is an image that should be shown in the browser. So the complete URL for this 1861 Colt would be:

https://sixshootercommunity.com/forum/images/uploaded/20210913141141613f5c1dc4160.jpg

If we take that url and enclose it in the image tags {img} and {/img} with no spaces and with the [ in place of the { and ] in place of the } we end up with an Apple acceptable image tag that results in an image appearing where before there was none. Like so:

So now we know what's happening so folks can't see the pictures that are uploaded onto our server. What I DON'T know is how to fix the forum system so that it would use the longer URL when inserting images into a post. When done manually it apparently works just fine.