The discussion revolves around an error message Discourse::InvalidAccess when uploading images with HEVC compression. Roi initially encountered the issue when trying to upload edited photos from an iPhone. Falco explained that HEVC images work in Discourse if they have the correct .heif extension, but not when using the .jpeg extension. Roi attempted to upload a renamed photo with the .heif extension, which was still not supported. Falco suggested taking a picture directly from the phone and uploading it to test the issue. Roi agreed to try this, but also pointed out that the use case of editing photos before uploading is common. In later posts, Roi successfully uploaded a photo directly from the iPhone, and Roi uploaded a renamed photo with the .heic extension, which revealed a different error message than initially encountered. The issue appears to be related to the file extension and compression used in the images.
I tried to upload some images into a post and always got the message Discourse::InvalidAccess.
When I looked closer, I noticed that the JPG files use the HEVC compression. Then I remembered that I made the photos with an iPhone and edited the photos before sending them out via email.
Uploading the photos after resaving them as JPG file on Windows worked. So it has to be something with the HEVC compression. Maybe the file extension .jpeg which Apple Mail chose is not okay, too?
Anyway, the error message is not user friendly when it comes to “normal” users. Is there a way to change that?
Also, is it possible to support HEVC in Discourse?
Images with HEVC compression already work in Discourse, they are converted to JPG in the backend. But those should be properly identified with the .heif extension.
AFAIK having HEVC compression in a JPG container is not valid.
Can you try to take a picture from your phone in HEVC and upload it directly here?
Images that have been manipulated and transformed by one of more programs may just be invalid. I suggest taking a picture with your phone and trying to upload that, which is the flow that is common for most users.
Well, but that is the typical usecase. So it should work in my eyes.
I will try. Later. The iPhone is at home.
And I will also try to edit a photo and upload it. It is also interesting for me to know where the problem comes from.
But as I said, it is not something total uncommon what happened here… Starting with never altering the file extension, as everything happened on the iPhone.
Interesting. And a different message than what I got in my own forum. And because the photo with the USB sticks is also HEVC/HEIC, but uploaded as IMG_1018.jpg (I was able to see this when it was uploaded).
So it should work in my eyes.
