Critical error after update to v1.10.1

  • Resolved erikggonc

    (@erikggonc)


    3 years, 9 months ago

    Hello, I have installed version 1.9.53, and after updating to version 1.10.1 the warning that there is a critical error on my website appeared.
    In my error_log file there is the following alert:

    [19-Feb-2021 04:35:36 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function foogallery_thumb_active_engine() in /home2/mysite/public_html/wp-content/plugins/foogallery/includes/thumbs/class-foogallery-thumb-manager.php:17
Stack trace:
#0 /home2/mysite/public_html/wp-includes/class-wp-hook.php(287): FooGallery_Thumb_Manager->init_active_engine('')
#1 /home2/mysite/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
#2 /home2/mysite/public_html/wp-includes/plugin.php(484): WP_Hook->do_action(Array)
#3 /home2/mysite/public_html/wp-settings.php(420): do_action('plugins_loaded')
#4 /home2/mysite/public_html/wp-config.php(104): require_once('/home2/mysite...')
#5 /home2/mysite/public_html/wp-load.php(37): require_once('/home2/mysite...')
#6 /home2/mysite/public_html/wp-cron.php(44): require_once('/home2/mysite...')
#7 {main}
  thrown in /home2/mysite/public_html/wp-content/plugins/foogallery/includes/thumbs/class-foogallery-thumb-manager.php on line 17

    What shoul I do?

    Thank you in advance for your help.

Viewing 15 replies - 1 through 15 (of 21 total)
  • Thread Starter erikggonc

    (@erikggonc)

    I just received an automatic message from wordpress with the following error detail:

    An error of type E_COMPILE_ERROR was caused at line 39 of the file /home2/mysite/public_html/wp-content/plugins/foogallery/freemius/includes/fs-essential-functions.php. Error message: require_once(): Failed opening required '/home2/mysite/public_html/wp-content/plugins/foogallery/freemius/includes/supplements/fs-essential-functions-2.2.1.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear')

    I hope this can help to fix the problem.

    Thanks again.

    Hi @erikggonc

    I have looked at your error messages and after analyzing them, realized that this error is being caused because during the update it appears that some of the files somehow got corrupted and some of them are now missing.

    To fix this, I’d like to kindly ask you to delete the FooGallery plugin from your site and then reinstall it again and don’t worry, your data won’t be lost since it is stored in the database.

    Please try this and let us know how it goes.

    Kind regards,
    Elvis

    Thread Starter erikggonc

    (@erikggonc)

    I disabled the plugin, deleted it, asked to install from the “add new plugin” menu and even then the error occurs.
    I had to overwrite the last functional version to get my site back online.

    Plugin Author bradvin

    (@bradvin)

    Hi @erikggonc

    With the old version installed, pls goto FooGallery -> System Info and paste the result you get here. This will help us replicate your environment and hopefully reproduce the error.

    Sorry for the inconvenience but hopefully we can get you back up and running on the latest version ASAP

    This latest update caused critical errors on about 20 of my websites. What a complete nightmare. I’ve had to delete the plugin from the filemanager, login to the dashboard and reinstall it.

    Please guys carry out more testing before launching an update!!

    Thanks

    Plugin Author bradvin

    (@bradvin)

    hi @klwd

    Sorry for the problems. We did do a lot of testing before this release, but it seems we cannot test every scenario/server setup.

    Can you provide some logs into what your error is?

    Thanks for your reply. The errors looked like this:

    [Fri Feb 19 06:17:14 2021] [error] [client 54.36.148.219:0] PHP Fatal error: require_once(): Failed opening required ‘/home/sites/3b/f/fc1ac71268/public_html/wp-content/plugins/foogallery/freemius/require.php’ (include_path=’.:/usr/share/pear’) in /home/sites/3b/f/fc1ac71268/public_html/wp-content/plugins/foogallery/freemius/start.php on line 482

    On a different website they said this

    [Thu Feb 18 20:24:52 2021] [error] [client 77.240.14.105:0] PHP Parse error: syntax error, unexpected ‘const’ (T_CONST), expecting variable (T_VARIABLE) in /home/sites/2b/7/7885ee489e/public_html/wp-content/plugins/foogallery/includes/class-foogallery-crop-position.php on line 12

    Hope that helps!

    Plugin Author bradvin

    (@bradvin)

    thanks @klwd

    I am not sure about the 1st error. That seems like a corrupt update, but I need to investigate more.

    The 2nd error was resolved in 1.10.1 which occurred when running PHP 5.6

    Did you manage to get it running on 1.10.1? Or did you have to roll back to a previous version?

    The 2nd error was the common one to be fair. But the plugin error email didnt get sent for some reason. It completly crashed the websites, and no way to safe mode.

    I had to rename the plugin folder, then login to the dashboard, update the plugin to latest, then reactive.

    The websites are running PHP 7.4.

    Many thanks

    @bradvin Can I email you please about a different matter? rob at klwd.co.uk or let me know your email address ?? Thanks!

    Thread Starter erikggonc

    (@erikggonc)

    Sorry for taking too long to respond. Busy day here.

    FooGallery version : 1.9.53
    WordPress version : 5.6.1
    Activated Theme : Dreamspa Child
    WordPress URL : https://mysite.com
    PHP version : 7.4.15
    PHP GD : Loaded (V2)
    PHP Imagick : Loaded
    PHP Open SSL : Loaded
    PHP HTTP Wrapper : Found
    PHP HTTPS Wrapper : Found
    HTTPS Mismatch : None
    PHP Config[allow_url_fopen] : 1
    PHP Config[allow_url_include] : 1
    WP Image Editor : WP_Thumb_Image_Editor_Imagick
    Thumbnail Generation Test : https://mysite.com/wp-content/uploads/layerslider/Dream-Spa-Slider/slider1-image.png
    Extensions Endpoint : https://raw.githubusercontent.com/fooplugins/foogallery-extensions/master/extensions.json?v=V4DjCXMByOhH
    Extensions Errors : Nope, all good
    Extensions :
    Extensions Active : Array
    (
    [0] => default_templates
    [1] => foobox-image-lightbox
    [2] => foobox
    )

    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
    )

    Settings : Array
    (
    [gallery_template] => default
    [gallery_sorting] =>
    [default_gallery_settings] => 0
    [caption_title_source] => caption
    [caption_desc_source] => desc
    [thumb_jpeg_quality] => 90
    [default_crop_position] => center,center
    [thumb_resize_upscale_small_color] => rgb(0,0,0)
    [language_imageviewer_prev_text] => Prev
    [language_imageviewer_next_text] => Next
    [language_imageviewer_of_text] => of
    [language_images_count_none_text] => No images
    [language_images_count_single_text] => 1 image
    [language_images_count_plural_text] => %s images
    [enable_custom_ready] => on
    [custom_js] =>
    [custom_css] =>
    [default_retina_support] => Array
    (
    [2x] => false
    [3x] => false
    [4x] => false
    )

    )

    Active Plugins : Array
    (
    [0] => worker/init.php
    [1] => foogallery/foogallery.php
    [2] => LayerSlider/layerslider.php
    [3] => Ultimate_VC_Addons/Ultimate_VC_Addons.php
    [4] => better-wp-security/better-wp-security.php
    [5] => colorlib-login-customizer/colorlib-login-customizer.php
    [6] => contact-form-7/wp-contact-form-7.php
    [7] => custom-facebook-feed/custom-facebook-feed.php
    [8] => designthemes-core-features/designthemes-core-features.php
    [9] => dt-reservation-plugin/dt-reservation-plugin.php
    [10] => duplicate-post/duplicate-post.php
    [11] => easy-wp-smtp/easy-wp-smtp.php
    [12] => envato-market/envato-market.php
    [13] => events-manager/events-manager.php
    [14] => flamingo/flamingo.php
    [15] => foobox-image-lightbox/foobox-free.php
    [16] => instagram-feed/instagram-feed.php
    [17] => iq-block-country/iq-block-country.php
    [18] => js_composer/js_composer.php
    [19] => kirki/kirki.php
    [20] => loco-translate/loco.php
    [21] => mailchimp-for-wp/mailchimp-for-wp.php
    [22] => menu-duplicator/menu-duplicator.php
    [23] => profile-builder/index.php
    [24] => revslider/revslider.php
    [25] => s2member/s2member.php
    [26] => simple-history/index.php
    [27] => unyson/unyson.php
    [28] => woo-combo-offers/woo-combo-offers.php
    [29] => woocommerce-correios/woocommerce-correios.php
    [30] => woocommerce-extra-checkout-fields-for-brazil/woocommerce-extra-checkout-fields-for-brazil.php
    [31] => woocommerce-pagseguro/woocommerce-pagseguro.php
    [32] => woocommerce/woocommerce.php
    [33] => wp-html-mail/wp-html-mail.php
    )

    Hi @erikggonc

    Thanks for sharing that with us.

    Just for further clarification, could you kindly confirm to us if the result that you have shared with us from FooGallery -> System Info is from a site that was going through the first or the second error message you mentioned to us earlier?

    Thanks in advance for that.

    Kind regards,
    Elvis

    Hi @klwd

    Regarding your request to email us, I’d like to kindly ask you to simply open up a new topic from here and explain to us the issue you are facing and we’ll gladly help you out with it as soon as possible.

    Looking forward to hearing from you.

    Kind regards,
    Elvis

    Thread Starter erikggonc

    (@erikggonc)

    Both messages are from the same site. The first one was from the error_log file. And the second was from e-mail digest, generated by wordpress itself, about the same error.

    If you want a temporary access, just let me know how can I send you the credentials in private.

    Thanks!

    Plugin Author bradvin

    (@bradvin)

    Please can you contact me on email : brad @ fooplugins . com

    so we can assist further

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘Critical error after update to v1.10.1’ is closed to new replies.