Can’t tell since you ninja edited your post which did not create a new revision. The first version of this post only has “edited.png”.
Which makes me think that you linked the image and did not upload it.
Yes, because you edited your post too quickly. We have a grace period window of 300 seconds here in which if you make an edit, it won’t create a new version of the post.
If you look at the raw, you see that the images are merely links to dropbox
The underlying links have long been deleted - Shouldn’t that mean these .gif should seize appearing? Clicking “View Image” from the context menu takes me to a community.signalusers address, is that expected behavior?
Testing, I’ll edit this out in ~300 seconds and shortly after delete the link.
deleted.png
Edit#2
The link is deleted but the image persists in the edit history, perhaps it doesn’t have an Upload record as it isn’t removed by the automatic cleanup.
I suppose, looking about, that it is held locally is expected behavior when download_remote_images_to_local is enabled. I think that’s the relevant setting.
So this
isn’t functioning for this type of upload, as demonstrated in my previous post. Correct me if I’m wrong.
clean up uploads sounds like a general setting that would capture all images with an upload record, is that correct? Not just those present due to download_remote_images_to_local. If true, I should be able to find examples on the site of regular image uploads that aren’t being removed as a result of the automatic cleanup.
You mind me asking what the clean orphan uploads grace period hours is set to here so I can offer it as a solution. Or does it come with a default?
If they decide to enable that setting, will they need to do anything to apply it to past posts?
Edit
Just for the sake of being explicit, the thinking here is that this isn’t an issue but that a setting needs to be switched on. I just don’t want to go back and say “You need to enable this!” and they say “It is enabled!” I’ll look silly.
I also caught myself frantically looking for a place to browse uploads (familiar with it from MediaWiki) because I just know stuff gets double triple and quadruple uploaded, and sometimes I wonder where a file was that I uploaded once a while ago but maybe lost or deleted so I can link to it instead of re-uploading it yet again… I guess there is something to be said about a file browser…
Também tive que excluir um arquivo carregado de alguma forma. Não temos a tarefa de limpeza ativada, pois alguns arquivos vêm de uma importação de um software de fórum diferente e ainda não foram referenciados corretamente em posts importados. Portanto, precisei encontrar uma maneira manual. O seguinte funciona, mas não é elegante…
Certifique-se de que o upload relevante não esteja mais na versão atual de nenhum post. Dessa forma, o Discourse o considerará órfão e não causará problemas ao excluí-lo.
Use o plugin Data Explorer ou outra maneira de consultar o banco de dados do Discourse para listar uploads órfãos, encontrar o relevante e anotar seu upload_id e filename. Consulta relevante:
SELECT
uploads.id, uploads.user_id, uploads.created_at,
uploads.url, uploads.filesize
FROM uploads
LEFT OUTER JOIN post_uploads ON uploads.id = post_uploads.upload_id
WHERE post_uploads.post_id IS NULL
ORDER BY created_at DESC
LIMIT 100
No banco de dados ou com o console Rails para Discourse, exclua o registro associado da tabela uploads pelo seu ID de upload. Aqui eu uso o console Rails:
Upload.where(id: 16384).first.delete
Exclua o arquivo associado, incluindo todas as versões otimizadas (se houver, aplica-se a imagens) do sistema de arquivos via SSH. Observe o curinga adicionado antes da extensão do arquivo para capturar também as versões otimizadas, que têm um sufixo aqui. Claro,
cd /path/to/discourse/shared/public/
find . -name 43adade7a4cc64426adb8232a56cb2c3b49fb7c9*.pdf -type f -delete
Huh! Parece que a imagem referenciada nesta postagem não é capturada por estas configurações:
Por que ela não foi excluída?
Posso também me perguntar por que o Discourse “faz upload” de um arquivo vinculado, como o link do Dropbox aqui? O objetivo de vincular um arquivo específico é, muitas vezes, manter o controle sobre o conteúdo.
Com a alteração de renomear post_uploads para upload_references, a consulta SQL listada na etapa 2 não é mais válida. O código atualizado é:
SELECT
uploads.id, uploads.user_id, uploads.created_at,
uploads.url, uploads.filesize
FROM uploads
LEFT OUTER JOIN upload_references ON uploads.id = upload_references.upload_id
WHERE upload_references.target_id IS NULL
ORDER BY created_at DESC
LIMIT 100
