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 `` like the following:
```plaintext
```
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?
---
> [@Arkshine](#):
>
> hotlinked
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](https://meta.discourse.org/t/2-9-0-beta5-security-fixes-block-hotlinked-media-pm-tagging-search-improvements-and-more/229845) I see there’s a `block_hotlinked_media` feature but I don’t really have that set.
---
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:
```plaintext
```
---
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.
---
```
---
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.
---
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.