Support » Plugin: Glossary » Fatal error after update of free ver. 2.0.1

  • Resolved rabbito03

    (@rabbito03)


    Hi,

    After the last update of version 2.0.1, I received an email with the following errors:

    Error Details
    =============
    An error of type E_ERROR was caused in line 331 of the file /public_html/wp-content/plugins/glossary-by-codeat/admin/includes/CMB2/includes/helper-functions.php. Error message: Uncaught Error: Class ‘CMB2_Hookup’ not found in /public_html/wp-content/plugins/glossary-by-codeat/admin/includes/CMB2/includes/helper-functions.php:331
    Stack trace:
    #0 /public_html/wp-content/plugins/glossary-by-codeat/admin/includes/CMB2/includes/helper-functions.php(363): cmb2_print_metabox_form()
    #1 /public_html/wp-content/plugins/glossary-by-codeat/admin/views/tabs/settings.php(244): cmb2_metabox_form()
    #2 /public_html/wp-content/plugins/glossary-by-codeat/admin/views/admin.php(71): require(‘/home/brdhandic…’)
    #3 /public_html/wp-content/plugins/glossary-by-codeat/admin/class-glossary-admin.php(94): include_once(‘/home/brdhandic…’)
    #4 /public_html/wp-includes/class-wp-hook.php(287): Glossary_Admin::display_plugin_admin_page()
    #5 /public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
    #6 /public_html/wp-includes/plugin.php(484): WP_Ho

    Errors On Site: Frontend/Administration
    =======================================
    Warning: include(/public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/../../integrations/ACF.php): failed to open stream: No such file or directory in /public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/ClassLoader.php on line 444

    Warning: include(): Failed opening ‘/public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/../../integrations/ACF.php’ for inclusion (include_path=’.:/opt/remi/php74/root/usr/share/pear:/opt/remi/php74/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/ClassLoader.php on line 444

    Warning: include(/public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/../../integrations/Widgets/Search.php): failed to open stream: No such file or directory in /public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/ClassLoader.php on line 444

    Warning: include(): Failed opening ‘/public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/../../integrations/Widgets/Search.php’ for inclusion (include_path=’.:/opt/remi/php74/root/usr/share/pear:/opt/remi/php74/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/ClassLoader.php on line 444

    Warning: include(/public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/../../frontend/Term_Content.php): failed to open stream: No such file or directory in /public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/ClassLoader.php on line 444

    Warning: include(): Failed opening ‘/public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/../../frontend/Term_Content.php’ for inclusion (include_path=’.:/opt/remi/php74/root/usr/share/pear:/opt/remi/php74/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /public_html/wp-content/plugins/glossary-by-codeat/vendor/composer/ClassLoader.php on line 444

    Any ideas?

    Lubo

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi Rabbit03,
    I am investigating the issue but seems that the first errors is about a previous version of the plugin, because refer to a folder that the new version don’t use anymore so maybe it is a cache issue.

    On the other error I am investigaint right now.

    Sorry for the issue I am releasing now a new version with the bugfix.

    The new 2.0 implement a new system on loading files to improve performance and other things but seems that our CI had some issues on generating a compatible free package for the plugin.

    Thread Starter rabbito03

    (@rabbito03)

    Thank you for your quick response.
    Everything is alright now!
    After the last update the plugin works like a charm.

    Kind regards

    Perfect, let me know if there are other issues but I hpw that the 2.0 now will work like a charm 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.