A user reports that image metadata is preserved in PNG uploads but stripped from JPG uploads on their Discourse site, despite having strip image metadata unchecked. Falco explains this is due to a conflict with the composer media optimization image enabled feature, which is incompatible with preserving metadata. After disabling this feature and refreshing the browser, the user confirms metadata is now retained in JPGs, though uploads become larger and slower. The user suggests a better configuration interface to prevent such conflicts. Falco acknowledges the issue and plans to implement a system to prevent contradictory settings, leaving the bug open for future resolution. Falco also references a related GitHub PR addressing the issue.
On this site:
I have the following File settings:
strip image metadata = UNCHECKEDpng to jpg quality = 100 (thereby disabled)I use ExifTool to set and read image metadata.
The metadata survives intact on my PNG uploads but not on my JPG uploads. And I believe this to be a bug.
Here is a PNG to check:
And a JPG to check:
But you should perform your own tests. And this should not be much work. HTH R
I gotta update the copy on that strip image metadata to warn about this.
Many thanks, @Falco. I need to explore this this evening. Discourse could perhaps go further and feature a popup or even a message if counteracting or counterintuitive settings are being made by admins?
We have a system where we can prevent contradictory settings from being toggled. Will leave this bug open so we can address this.
I just set the following parameter as suggested. And left the earlier settings as indicated above:
composer media optimization image enabled = UNCHECKEDAnd the problem seems to persist. I changed the EXIF data and filename and MD5 sum so there could be no memory in discourse, I imagine.
The site is also very close to its initial install, so most defaults persist. Any suggestions most welcome?
Have you refreshed the page after toggling it?
No, but I cannot try that right now. Thanks though.
@Falco Indeed refreshing my browser tab worked after updating the settings! It also seemed that the upload was considerably slower. And the downloaded file — with the metadata fully intact — was 10× the size when compared to previous iterations. All that makes sense, of course.
I realize that there are different use‑cases in play. The default behavior is useful for forums that are social in nature. But my application is to support science and research. And it is better that users make decisions about the appropriate format, resolution, and metadata for their various uploads. And that discourse simply passes the files through uncontaminated.
Given that there are logical bundles of settings, perhaps some kind of higher level configuration or interpretation would be useful?
Again, thanks for your support. And I guess you saw this recent posting too, regarding configuration hints:
Best, R
Here is a screenshot of the bundle of settings that prevents discourse from messing with uploaded files:
And don’t forget to refresh your browser tab too, to purge any client‑side functionality that might be present but no longer required.
