Fatal Error with latest update

I’m also having this trouble. I manually fixed the last issue with CMB2_Hookup (the uppercase/lowercase thing), but it all broke again after the latest update.
My diagnostics so far:
* Filename of CMB2_Hookup.php has uppercase H in /CMB2/includes (this is consistent with naming convention of other files in the folder)
* File CMB2_Hookup.php in /CMB2/includes declares class CMB2_hookup (lowercase H), though it extends CMB2_Hookup_Base (uppercase H).
* bootstrap.php in /CMB2 references has $hookup = new CMB2_hookup( $cmb ); – this is what’s causing code to look for CMB2_hookup.php

Actions I took to get it working on my site
* Change bootstrap.php line 62 to $hookup = new CMB2_Hookup( $cmb );
* Change class definition in CMB2_Hookup.php to class CMB2_Hookup extends CMB2_Hookup_Base {
* Update lines 357, 361 in helper-functions.php to CMB2_Hookup::enqueue_cmb_css(); and CMB2_Hookup::enqueue_cmb_js(); respectively.

After this, I can view and edit sermons again, although I am still getting unexpected edit-screen appearance and error messages on saving.

Devs: I am happy to provide more information and work with you, but would dearly love to see this fixed.

I also had to revert back to a previous version…

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Sermon Manager for WordPress.

First, visit your website (https://ccfergusfalls.com/) and check for any visible issues. Next, visit the page where the error was caught (https://ccfergusfalls.com/wp-admin/options-general.php?page=wpsupercache&tab=contents&wp_delete_cache=1&_wpnonce=628e85dc12) and check for any visible issues.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.5
Current theme: Vantage (version 1.15.1)
Current plugin: Sermon Manager for WordPress (version 2.16.1)
PHP version 7.4.9

Error Details
=============
An error of type E_ERROR was caused in line 62 of the file /srv/disk9/1559351/www/ccfergusfalls.com/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/bootstrap.php. Error message: Uncaught Error: Class ‘CMB2_hookup’ not found in /srv/disk9/1559351/www/ccfergusfalls.com/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/bootstrap.php:62
Stack trace:
#0 /srv/disk9/1559351/www/ccfergusfalls.com/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/init.php(158): cmb2_bootstrap()
#1 /srv/disk9/1559351/www/ccfergusfalls.com/wp-includes/class-wp-hook.php(287): CMB2_Bootstrap_270->include_cmb(”)
#2 /srv/disk9/1559351/www/ccfergusfalls.com/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
#3 /srv/disk9/1559351/www/ccfergusfalls.com/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#4 /srv/disk9/1559351/www/ccfergusfalls.com/wp-settings.php(546): do_action(‘init’)
#5 /srv/disk9/1559351/www/ccfergusfalls.com/wp-config.php(92): require_once(‘/srv/disk9/1559…’)
#6 /srv/disk9/1559351/www/ccfergusfalls.com/wp-load.php(37): require_once(‘/srv/disk9/1559…’)
#7 /srv/disk9/1559351/www/ccfergusfalls.com/wp-admin/admin.php(34): require_once(

Same thing happened to me when I updated.

Hello,

I also get the fatal error after the latest update. I am using Vertex theme from Elegant Themes and WordPress 5.5. I have to disable this plugin to get my WordPress Dashboard back up.

Regards
Dean Hall

• This reply was modified 4 years, 3 months ago by OYM.

Same here

Happened to me as well. What do we do to fix it? Here’s what I get when trying to get to dashboard:

Warning: include_once(/homepages/28/d218648728/htdocs/ministry/morrow/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/includes/CMB2_hookup.php): failed to open stream: No such file or directory in /homepages/28/d218648728/htdocs/ministry/morrow/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/includes/helper-functions.php on line 48

Warning: include_once(): Failed opening ‘/homepages/28/d218648728/htdocs/ministry/morrow/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/includes/CMB2_hookup.php’ for inclusion (include_path=’.:/usr/lib/php7.4′) in /homepages/28/d218648728/htdocs/ministry/morrow/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/includes/helper-functions.php on line 48

Fatal error: Uncaught Error: Class ‘CMB2_hookup’ not found in /homepages/28/d218648728/htdocs/ministry/morrow/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/bootstrap.php:62 Stack trace: #0 /homepages/28/d218648728/htdocs/ministry/morrow/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/init.php(158): cmb2_bootstrap() #1 /homepages/28/d218648728/htdocs/ministry/morrow/wp-includes/class-wp-hook.php(287): CMB2_Bootstrap_270->include_cmb(”) #2 /homepages/28/d218648728/htdocs/ministry/morrow/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array) #3 /homepages/28/d218648728/htdocs/ministry/morrow/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #4 /homepages/28/d218648728/htdocs/ministry/morrow/wp-settings.php(546): do_action(‘init’) #5 /homepages/28/d218648728/htdocs/ministry/morrow/wp-config.php(92): require_once(‘/homepages/28/d…’) #6 /homepages/28/d218648728/htdocs/ministry/morrow/wp-load.php(37): require_once(‘/homepages/28/d…’) #7 /homepages/28/d2186487 in /homepages/28/d218648728/htdocs/ministry/morrow/wp-content/plugins/sermon-manager-for-wordpress/includes/vendor/CMB2/bootstrap.php on line 62
There has been a critical error on your website. Please check your site admin email inbox for instructions.

Learn more about debugging in WordPress.

Same issue for us.

It seems as though the most reliable way to fix it is to revert to a previous version of the plugin. However, if you have access to the plugin files, you can also follow the three steps I took in my response above (https://www.ads-software.com/support/topic/fatal-error-with-latest-update-7/#post-13304375) and that should get things working again.

What is the best way to revert to a previous version? I am able to use FTP. Just need to know where to get the files and what version to use. Also, will all the sermon files remain the same?

Same issue here. Thanks for @almcnicoll for the work-around, it worked for me just as you said and I was able to login to my site. However, after doing the edits, I tried to add a new sermon and that interface was not working – no Save Draft option, the very top of the page had what looked like a standard Post interface with the title and content above the normal sermon fields. So in the end, I reverted to the previous version (2.16.0) from last night’s backup.

Hopefully the @wpforchurch folks are listening and release an update soon that fixes this issue. I did notice that they say that they have tested up to WordPress 5.4.2 but my site automatically updated to WordPress 5.5 a while back, so it may be that there are some compatibility issues still to be resolved. For now, I’ll stick to 2.16.0 as it seems to be working for me.

• This reply was modified 4 years, 3 months ago by beryrinaldo. Reason: added more details

+1 to @almcnicoll
Thanks.

I have also had the same fatal error and am glad to see I’m not the only one. I have reverted to a previous version (2.16.0) and hope they’ll fix this issue in a future update.

Hi All,

We have the same issues, but we can’t log in and revert to the previous version…..
Tried special recovery link in the e-mail and still get an error.

We also get an odd situation where after the login has failure if we revisit our public site normally without logging in it give the appearance that it has logged in but we aren’t able to access the dashboard or WordPress it’s self, it just displays the error message there is a fault.

So we have a working website to the public, be we are unable to login, update or revert the plugin back.

Any ideas?

Can you post the exact text of any error messages you’re receiving?
I’m far from an expert in WordPress, but I’ve done a lot of work on this particular bug one way or another, and might be able to help.

Same problem here with 2.16.1 … back to version 2.15.15 in the meantime.
Please fix this issue !