Turn off image links validation?

Product Support

AI-generated summary

The discussion revolves around an issue with image links in cooked content on a Discourse platform. avaldez reported that custom image links are being replaced with a “broken image” span during the cooking process, despite being valid. Arkshine suggested checking the “block hotlinked media” setting, but avaldez couldn’t find it in the UI.

After sharing their Discourse version (2.4.0.beta6) and image tag format, avaldez eventually found a solution: including the hostname in the image link. This prevents Discourse from modifying the img elements in the cooked version, even if it can’t access the resource. avaldez thanked Arkshine for their help.

1

Hi guys, I’m having issues with the cooked content of posts with images.

The thing is that we are using a custom link for images looking like:
/api/v1/discourse/custom/link/hash_id/filename.png

Everything good when the post is created, but there’s a point while discourse is cooking that post html, that detects that this link is “broken”, so it replaces it’s content with a <span> like the following:

<span class="broken-image" title="This image is broken">
<svg class="fa d-icon d-icon-unlink svg-icon" aria-hidden="true"><use xlink:href="#unlink"></use></svg>
</span>

This is not happening on file uploads, so I’m wondering if there’s a way to disable this validation to keep cooked version intact?

2

Have you enabled the block hotlinked media setting?

3

I don’t, and I can’t find that setting in the UI, is there a special place to look for it?

Looking on this thread I see there’s a block_hotlinked_media feature but I don’t really have that set.

image
image1894×1000 103 KB

4

Can you share your Discourse version exactly?

It’s unlikely – is there a chance your image domain prevents hotlinked images?

5

Sounds like it, I’m aware we are using an old version 2.4.0.beta6, we have plans to upgrade, but not just yet.

These image tags look like:

<img src="/api/v1/discourse/custom/link/hash_id/filename.png" width="452" height="409">
6

The solution to this issue was to include the hostname for the image, to have the full link. That way, even if discourse doesn’t have access to the resourse, it is not messing with img elements in the cooked version.

@Arkshine I appreciate your help.