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
{{ message }}
This repository has been archived by the owner on Apr 15, 2021. It is now read-only.
For some reason this URL does not get recognised as an image, and isn't launched by Nivo lightbox. Instead, it just opens the image as a separate link.
as an update I've confirmed that the issue is caused due to the ?ssl=1 on the URL.
I've updated the title to make this clearer.
Does Nivo need to be updated to gracefully handle that, and still recognise that this is an image?
brencecoghill
changed the title
Jetpack photon image with Https not recognised as "image"?
Image served from Jetpack photon has "?ssl=1" on end of URL and won't load in lightbox
Sep 11, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Related link: https://www.sandbox.imageworkshop.com/projects/william-angliss-institute/
Nivo works fine with Jetpack photon turned off.
When I turn on Jetpack photon, the image URL is updated to be "https://i0.wp.com/www.sandbox.imageworkshop.com/wp-content/gallery/case-study-william-angliss/wai-course-guide-pg14.jpg?ssl=1"
For some reason this URL does not get recognised as an image, and isn't launched by Nivo lightbox. Instead, it just opens the image as a separate link.
The following error is displayed in the console:
Resource interpreted as Document but transferred with MIME type image/webp: "https://i0.wp.com/www.sandbox.imageworkshop.com/wp-content/gallery/case-study-william-angliss/wai-course-guide-pg14.jpg?ssl=1".
you can see details on this page. I'm not sure how to resolve this?
I found this answer, which might be related - I'm just not sure how to implement it for NIVO?https://stackoverflow.com/questions/13985003/resource-interpreted-as-document-but-transferred-with-mime-type-image-jpeg
The text was updated successfully, but these errors were encountered: