Foo Galleries not displaying
-
I don’t know if this had to do with the recent upgrade or what, but all of a sudden, none of my Foo Galleries are displaying. This is happening on quite a few of my pages, but one example is urbancraftuprising.com/stock-photos. You can see many headings with no photos beneath them even though there should actually be a gallery beneath each one.
The photos that you do see displaying on the page are using a different kind of gallery–not FooGallery.
Please help!
The page I need help with: [log in to see the link]
-
Same thing is happening to me. I updated WordPress and the galleries are not working now. I also tried to deactivate the other plugins. Links are all there but there is just a white box where the image should be and it looks like the masonry is not styling its self. Do they see this reply or should I make a new ticket?
I added all our foo galleries urls but that post has been held in moderation for 72 hours by forums so here is the first one: https://www.metroblindsport.org/adventure-sports/
Hi All,
There’s a few different errors here presenting in a similar fashion so I’ll try answer each separately but first I’ll explain the reason behind the majority of the problems listed so you can better understand the issue.
In 1.4.x we added advanced loading of images which relies on JS to determine which images should be loaded and when etc. so the JS must be initialized in order for the images to be displayed which is normally not a problem. At the moment to initialize the JS we rely on jQuery’s ready callback functionality however there is a drawback to using this method. Internally jQuery stores all ready callbacks in an array and then when needed it simply loops through and executes each one. The problem with this is that if two plugins, A and B, are both using the callback and plugin A’s initialize code throws an error, plugin B’s initialize code will never be run.
@ristretto6, @jeuriss, @saulwynne this is the reason FooGallery is not being initialized on your pages. You can see this by opening up the console in your browser and executing the following which will then load your galleries:
jQuery(".foogallery").foogallery().We will be adding in an option to use a custom ready callback instead of the jQuery one which will work around this issue so themes or other plugins failing do not prevent the galleries from loading. I’ve outlined below each of your individual issues in more detail.
@jeuriss the error on your page is being thrown by the jQuery migrate plugin due to a selector being used in the Fusion menu JS which is part of your theme. In the ~/wp-content/themes/Avada/Avada/assets/js/main.min.js they are using the following selector:
".fusion-menu a:not([href=#], .fusion-megamenu-widgets-container a, .search-link), .fusion-mobile-nav-item a:not([href=#], .search-link), .fusion-button:not([href=#]), .fusion-one-page-text-link:not([href=#])"which according to the migrate documention is invalid due to the use of[href=#], the#needs to be quoted.@saulwynne the error on your page is being thrown by the ~/wp-content/themes/metro/js/sidebar-height.js but can be easily fixed. At present the initialize code is attempting to use the shorthand for jQuery which is simply
$however in WordPress jQuery does not register the shorthand in order to avoid conflicts. To fix this error line 4 in the above mentioned file needs to be changed fromjQuery(document).ready(function(jQuery) {tojQuery(document).ready(function($) {@ristretto6 the error on your page is two fold. First the error preventing the initialize is being thrown by the ~/wp-content/themes/HighendWP/scripts/jquery.custom.js file on line 1529 where it is attempting to initialize a plugin called autocomplete which is supposed to be used for the header menu ajax search. The second part to your issue is a little more complicated and I have not found a solution yet. If you run the code
jQuery(".foogallery").foogallery()in your console you will get another error saying “Masonry is not defined”. For some reason on your site Masonry is not registering itself on the window object and so can’t be initalized using it’s class name. I’ll need to figure what is going on however I think it is due to your theme including Isotope and us including Masonry.@mwinterstorm I believe your issue is different to the above. On your page there is no FooGallery JS being included in the page at all. I’m just confirming with @bradvin about possible causes.
@carrosparaeventos could you provide me with a url?
Thanks
- The topic ‘Foo Galleries not displaying’ is closed to new replies.
