I’m not sure if this can be called a bug, but it is an unexpected behavior: Steps to reproduce: Add a new file extension like tif to authorized_extensions Attach a file with that extension to a post Remove the file extension from authorized_extensions Rebake all posts using rake posts:rebake Exp…

This is now fixed: https://github.com/discourse/discourse/pull/3573

Mmm, I think that lowering the max image size should be a supported action.

Re-enabling those file extensions is easier said then done. Rebake doesn’t throw any error. So, this gets only noticed if you take a look at the Sidekiq queue and realize that there are way too many tasks in the retry queue. And then you need to figure out which file extensions are missing. The er…

Das erneute Backen von Beiträgen schlägt fehl, wenn Anhänge nicht mehr erlaubt sind

Unterstützung

codinghorror (Jeff Atwood) 24. Juni 2015 um 23:45 2

Hmm, you might need to re-enable that filetype before rebaking. I don’t know if I would classify this as a bug.

Thema		Antworten	Aufrufe
Misleading message when image size limit changed Bug	3	790	24. Februar 2020
Some linked images not displaying/show as broken Support	8	1904	21. März 2022
Indication of email attachment with non-allowed extension Feature	5	1198	8. Oktober 2018
Rebake with rails command or rake task doesn't work, but rebuilding HTML does. Why? Self-hosting	9	2142	27. März 2022
Fixing Broken Images -- Summary of Steps? Support	4	1117	25. April 2022

Das erneute Backen von Beiträgen schlägt fehl, wenn Anhänge nicht mehr erlaubt sind

Verwandte Themen