Seeing the same thing for other lightbox scripts as well.
Thread Starter
G P
(@wetapplemedia)
The v2.2.0 download from your website is correct and works flawlessly, but the Automatic Update version 2.2.0 that downloads from WordPress has a file structure that is corrupted in some way.
-
This reply was modified 2 years, 7 months ago by
G P.
I can confirm that: the update is broken, the zip on the website is working fine. I hope you can fix this asap or you’ll have a ton of support tickets. 😉
Version 2.2.0 installed on my site has javascript and css in js and css directories.
The links to them output by responsive-lightbox does not have these directories in them.
For example…
The file is at…
/wp-content/plugins/responsive-lightbox/assets/prettyphoto/js/jquery.prettyPhoto.min.js
The link is…
/wp-content/plugins/responsive-lightbox/assets/prettyphoto/jquery.prettyPhoto.min.js
As @cafeine was saying the zip for 2.2.0 at…
https://downloads.wordpress.org/plugin/responsive-lightbox.2.2.0.zip
has css and js in css and js directories
The zip for 2.2.0 at…
https://downloads.wordpress.org/plugin/responsive-lightbox.zip
has js and css NOT in js and css directories.
Need the working version as 2.2.1
-
This reply was modified 2 years, 7 months ago by
wallyO.
-
This reply was modified 2 years, 7 months ago by
wallyO.
As @cafeine and @wallyo suggested, downloading the .zip file directly from their website worked as far as bringing up the lightbox. However, then my youtube videos weren’t coming up. I looked in the console after bringing the lightbox up and there’s the good ol’ mixed content error! However, the url I had put for the YouTube video does have https. The problem is in assets > tosrus > jquery.tosrus.min.js on line 83. <iframe src=”http://www.youtube.com/embed/ should be <iframe src=”https://www.youtube.com/embed/.
-
This reply was modified 2 years, 7 months ago by
pfeilal23.
-
This reply was modified 2 years, 7 months ago by
pfeilal23.
This issue should be fixed in just relesed v2.2.1.
Please update
Automatic update occurred for me.
Version 2.2.1 corrects the issues I described.
Thanks for the prompt update and thanks for the great plugin.
Thread Starter
G P
(@wetapplemedia)
Yes version 2.2.1 seems to have it fixed.