JS error and only first thumbnail shows with v2.0.35

Hi @wpuser362,

Thanks for contacting us.

Have you tried to enable the Custom Ready event? Enabling this can sometimes help when your galleries have trouble initializing. This could potentially happen when there are javascript errors on a page. You can find this setting in your wp-admin. Go to FooGallery -> Settings under Advanced tab, enable “Custom Ready Event” and click Save Settings.

Have you also tried to check if there is a plugin conflict that is resulting in the error? To check for a plugin conflict, you can try following the instructions in our plugin documentation: https://fooplugins.com/documentation/general/general-troubleshooting/health-check-debug/

If the problem persists, would you mind sharing with us the system info? You can find this in FooGallery > System Info. Please copy this and paste it here so we can investigate further.

Kind Regards,
Nathan.

Hi Nathan, thanks for the reply.

Custom Ready Event checkbox was already ticked

Used health check, disabled all plugins and enabled Foogallery first and the issue still persisted.

This is the output from System Info

FooGallery version : 2.0.35
WordPress version : 4.9.18
Activated Theme : Beaver Builder Child Theme
WordPress URL : https://dial-a-digger.co.uk
PHP version : 7.4.16
Thumb Engine : 
PHP GD : Loaded (V2)
PHP Imagick : Not found!
WP Image Editor : FooGallery_Thumb_Image_Editor_GD
Thumbnail Generation Test : https://dial-a-digger.co.uk/wp-content/uploads/2018/07/11707870_822383031210761_6470798379621896127_o.jpg
HTTPS Thumb Mismatch : None
Available Image Editors : Array
(
    [0] => EWWWIO_Imagick_Editor
    [1] => EWWWIO_GD_Editor
    [2] => FooGallery_Thumb_Image_Editor_Imagick
    [3] => FooGallery_Thumb_Image_Editor_GD
)

PHP Open SSL : Loaded
PHP HTTP Wrapper : Found
PHP HTTPS Wrapper : Found
PHP Config[allow_url_fopen] : 1
PHP Config[allow_url_include] : 1
Extensions Active : Array
(
    [0] => default_templates
)

Gallery Templates : Array
(
    [0] => default
    [1] => image-viewer
    [2] => justified
    [3] => masonry
    [4] => simple_portfolio
    [5] => thumbnail
    [6] => polaroid_promo
    [7] => grid_promo
    [8] => slider_promo
)

Lightboxes : Array
(
    [foogallery] => FooGallery PRO Lightbox (Not installed!)
    [foobox] => FooBox (Not installed!)
)

Settings : Array
(
)

Active Plugins : Array
(
    [0] => bb-plugin/fl-builder.php
    [1] => bb-ultimate-addon/bb-ultimate-addon.php
    [2] => call-now-button/call-now-button.php
    [3] => duplicator-pro/duplicator-pro.php
    [4] => ewww-image-optimizer/ewww-image-optimizer.php
    [5] => foogallery/foogallery.php
    [6] => litespeed-cache/litespeed-cache.php
    [7] => mainwp-child/mainwp-child.php
    [8] => really-simple-ssl/rlrsssl-really-simple-ssl.php
    [9] => redirection/redirection.php
    [10] => search-and-replace/inpsyde-search-replace.php
    [11] => updraftplus/updraftplus.php
    [12] => wordfence/wordfence.php
    [13] => wordpress-seo/wp-seo.php
    [14] => wp-mail-smtp/wp_mail_smtp.php
)

Hi @wpuser362

Thanks for sharing the System Info with us. I’d also like to kindly ask you to enable FooGallery Debug Comments for us.

To do so, kindly navigate to FooGallery -> Settings -> Advanced and click on the “Enable Debug” checkbox option as shown in this image: https://prnt.sc/13plwaa

Don’t forget to save changes. This will help us investigate this issue further. Once done, kindly let me know.

Thanks in advance.

Kind regards,
Elvis`

That’s debugging enabled now

Hi @wpuser362

From the System Info, I can see that you are using an outdated version of WordPress.

The issue causing this is that the WordPress version you are currently using is using quite an old version of jQuery 1.12.4. WordPress 5.5 and above uses jQuery 3+ and the .catch method mentioned in the error is only available in 3+

We are currently working on fixing this minor issue to make FooGallery backwards compatible too, but for now, I’d like to kindly ask you to upgrade your WordPress version to at least version 5.5 to prevent this from happening.

Thanks.

Kind regards,
Elvis.

We picked this example as it was the oldest version of WordPress we could find but the issue happens in all versions up to 5.5 which was only replaced at the end of January this year.

Hi @wpuser362

I’m glad to inform you that we have released an update that resolves this issue for you.

Kindly update your plugin to the latest version (Version 2.0.37) to permanently fix this issue.

Thanks.

Kind regards,
Elvis