We use the S3 storage adapter in our installation of Omeka, and found that when using less permissive versions of Mirador, manifests were not accepted by the viewer because they lacked an image height and width. Looking at the code, it seems that when there isn't an existing canvas JSON, the height and width are determined with a php getimagesize call that assumes the images are stored locally. Since ours aren't the call fails, and the height and width remain at their initial value of zero. It seems possible to fix by generating the height and width from the image metadata already stored in Omeka instead.
dicksonlaw583
commented
6 months ago
We use the S3 storage adapter in our installation of Omeka, and found that when using less permissive versions of Mirador, manifests were not accepted by the viewer because they lacked an image height and width. Looking at the code, it seems that when there isn't an existing canvas JSON, the height and width are determined with a php
getimagesizecall that assumes the images are stored locally. Since ours aren't the call fails, and the height and width remain at their initial value of zero. It seems possible to fix by generating the height and width from the image metadata already stored in Omeka instead.