-
-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Images flipped 90 degrees #600
Comments
Are you taking pictures with iPhone, which seems to have incorrectly rotated EXIF information? |
To assist (as a workaround and troubleshooting)... I also have this issue with most (but not all) portrait images taken on my Android phone. I believe this indicates it is an EXIF issue. I am uncertain if the Android EXIF data needs to be fixed, or if there is another orientation indicator Huge can use. |
I have seen this commented from time to time in the discussions and there's a lot on the Hugo Discourse about it too. There seems to be issues with how EXIF data is interpreted and that Hugo doesn't rotate the images to match the EXIF orientation. I might have to see if I can add this logic to the theme itself. See https://discourse.gohugo.io/t/image-exif-orientation/22902 for details. |
This issue has been automatically marked as stale because it has not had any recent activity. |
https://gohugo.io/functions/images/autoorient/ I would find a way to opt-in to this behavior. You don't need to run every image on every site through this filter. Maybe use a site param to opt-in for the whole site, or a page param to opt-in for a particular page. |
Issue description
Images taken horizontally show up fine, but anything taken vertically is rendered horizontally.
The code is simply:
I feel like this can't be standard behavior, so maybe I accidentally changed a configuration file without realizing it. Otherwise, it might have to do with the way the theme tries to make all the images the same width.
Theme version
v2.6.1
Hugo version
hugo v0.112.1+extended
Which browser rendering engines are you seeing the problem on?
Chromium
The text was updated successfully, but these errors were encountered: