# Broken images move to tombstone

**URL:** https://meta.discourse.org/t/broken-images-move-to-tombstone/117779
**Category:** Support
**Created:** [15 mei 2019 om 08:04 UTC](https://meta.discourse.org/t/broken-images-move-to-tombstone/117779 "2019-05-15T08:04:43Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![vinothkannans](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vinothkannans/32/86465_2.png) [@vinothkannans](https://meta.discourse.org/u/vinothkannans)
#### Post date: [21 mei 2019 om 15:47 UTC](https://meta.discourse.org/t/broken-images-move-to-tombstone/117779/14 "2019-05-21T15:47:22Z")

</div>

> [@Lure](#):
>
> Why are images moved in tombstone at the first place?

Looks like [topic-previews plugin](https://meta.discourse.org/t/topic-list-previews/101646) adds `PostUpload` record in [`update_post_image`](https://github.com/angusmcleod/discourse-topic-previews/blob/master/lib/cooked_post_processor_edits.rb#L76-L81) method. But after that [`link_post_uploads`](https://github.com/discourse/discourse/blob/0e677daaee3422ac056c3dac1b5bd23a53c4efc2/app/models/post.rb#L873-L878) method removes all existing post\_uploads before re-generating it. [This change](https://github.com/discourse/discourse/commit/434035f167eb15f3e2d8c6a52577d66d0e140b71) in the core triggered this issue. I think the plugin code must handle this to prevent image losses.

@appcomqa do you have any custom plugins installed? And are you in the latest version of Discourse?

---

_[View the full topic](https://meta.discourse.org/t/broken-images-move-to-tombstone/117779)._