WP Cron Fatal Error

Replies
3
Voices
3
Freshness
Followers

0

I’m receiving these Your Site is Experiencing a Technical Issue emails daily

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,
Discussion Board.

When seeking help with this issue, you may be asked for some of the
following information:
WordPress version 5.8.1
Current theme: Yas Elementor (version )
Current plugin: Discussion Board (version 2.4.2)
PHP version 7.4.24

Error Details
=============
An error of type E_ERROR was caused in line 105 of the file
/nas/content/live/brwpro/wp-content/plugins/wp-discussion-board/includes/classes/admin/class-admin.php.
Error message: Uncaught Error: Call to undefined function
WPDiscussionBoard\Admin\wpdbd_general_page_settings() in
/nas/content/live/brwpro/wp-content/plugins/wp-discussion-board/includes/classes/admin/class-admin.php:105
Stack trace:
#0 /nas/content/live/brwpro/wp-includes/class-wp-hook.php(303):
WPDiscussionBoard\Admin\Admin->register_options_init(”)
#1 /nas/content/live/brwpro/wp-includes/class-wp-hook.php(327):
WP_Hook->apply_filters(NULL, Array)
#2 /nas/content/live/brwpro/wp-includes/plugin.php(470):
WP_Hook->do_action(Array)
#3 /nas/content/live/brwpro/wp-content/plugins/wpmudev-updates/includes/class-wpmudev-dashboard-utils.php(135):
do_action(‘admin_init’)
#4 /nas/content/live/brwpro/wp-includes/class-wp-hook.php(303):
WPMUDEV_Dashboard_Utils->simulate_admin_actions(”)
#5 /nas/content/live/brwpro/wp-includes/class-wp-hook.php(327):
WP_Hook->apply_filters(NULL, Array)
#6 /nas/content/live/brwpro/wp-includes/plugin.php(470):
WP_Hook->do_action(Array)
#7 /nas/content/live/brwpro/wp-settings.php(600): do_action(‘wp_l

  • Matt

    Hi Michael,

    Thanks for reporting this error. It looks like because the config/settings function is not defined in the same namespace as the admin class, it's throwing an error on your environment. I am unable to replicate this on my side, however I will implement a fix to make sure that it looks for the config/settings function in the global namespace. This should fix the error you are seeing.

    This will go out in the next release.

    Thanks,

    Matt

  • Matt

    Hi Michael,

    As discussed over email. this issue seems to be related to WordPress crons. We will have a fix going out in the next version.

    Thanks!