Hi @gonzaguegb
This is not caused by FooBox, but rather from a conflict with another plugin or theme that is forcing your javascript files to load using the defer attribute.
It is usually a performance or caching plugin that does this on every script included in the page. I have also seen themes that include some custom php in the functions.php that does this.
Because FooBox loads some inline Javascript (based off the settings) the order of the scripts are loaded incorrectly, and the FooBox init code ends up being run before the FooBox script is loaded in the page, which causes the error you are getting.
I am sorry for this issue, but there is nothing we can do on our side to correct, unless we rewrite the way FooBox is initialized. This is something we are looking at doing in the next major release.
Send me your URL, so I can tell you if your site has this same conflict issue
Hi, here you are the URL http://www.tokyostreetview.com/uchiko (Testing a new page). But I think the problem may either be Jetpack from WordPress or The way that cloudflare handle things…
Cheers
Please can you try this updated version which tries to cater for when other themes or plugins change the foobox scripts to load in a deferred manner.
https://dl.dropboxusercontent.com/u/10968155/foobox-image-lightbox-free.1.2.23.zip
Please let me know if that version works for you
Hi there!
This version fix indeed the problem! Thanks!
Hi, I had the same problem. Probably because of the AutoOptimize plugin and active caching of JavaScript files.
I tried your 1.2.23 version which works partly. I tried it in Chrome were it fixed the issue above. But still Firefox and IE11 aren’t working correctly. Any idea why?
@gonzaguegb don’t know if you have already seen it but it is also not working in FF on your page.
Can’t offer you a link currently since I deactivated the caching and switched back to the 1.2.22 version due to necessary availability of the gallery feature.
-
This reply was modified 9 years, 2 months ago by
wolfio.
hey @wolfio
please update to 1.2.24 which fixes the problem on FF