You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, Piwigo 14.3.0 is unable to rotate HEIC photos by default and the method pwg.image.rotate reports the string [Image] unsupported file extension which is not a JSON data. It should either manage HEIC photos or report a JSON including an error message because this is problematic for third party apps like the iOS and Android apps (another issue).
Here are the steps to reproduce the issue from the UI:
Add 'heic' to $conf['picture_ext'] with the LocalFiles Editor plugin for enabling HEIC photos rotations,
Choose a HEIC photo from the web UI,
Request a rotation, e.g. 90° clockwise,
Check the corresponding files in the _data and upload folders.
The original HEIC image located in the upload folder is rotated as expected. But the thumbnail files located in _data are not deleted as the plugin does when dealing with JPEG files. The thumbnail shown on the web UI does not present the image rotated as expected. Force reloading the web page does nothing.
The text was updated successfully, but these errors were encountered:
First, Piwigo 14.3.0 is unable to rotate HEIC photos by default and the method
pwg.image.rotate
reports the string[Image] unsupported file extension
which is not a JSON data. It should either manage HEIC photos or report a JSON including an error message because this is problematic for third party apps like the iOS and Android apps (another issue).Here are the steps to reproduce the issue from the UI:
'heic'
to$conf['picture_ext']
with the LocalFiles Editor plugin for enabling HEIC photos rotations,_data
andupload
folders.The original HEIC image located in the upload folder is rotated as expected. But the thumbnail files located in _data are not deleted as the plugin does when dealing with JPEG files. The thumbnail shown on the web UI does not present the image rotated as expected. Force reloading the web page does nothing.
The text was updated successfully, but these errors were encountered: