PHP Fatal error: Uncaught Error: Call to undefined method maybe_wp_die

  • Resolved Oleksandr

    (@track77)


    5 months, 2 weeks ago

    Version Version 2.0.2

    [09-Jun-2024 18:59:48 UTC] PHP Fatal error: Uncaught Error: Call to undefined method MFM\Runners\File_Runner::maybe_wp_die() in /plugins/website-file-changes-monitor/vendor/deliciousbrains/wp-background-processing/classes/wp-background-process.php:551
    Stack trace: 0 /plugins/website-file-changes-monitor/vendor/deliciousbrains/wp-background-processing/classes/wp-background-process.php(335): WP_Background_Process->handle() 1 wp-includes/class-wp-hook.php(324): WP_Background_Process->maybe_handle() 2 wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 3 wp-includes/plugin.php(517): WP_Hook->do_action() 4 wp-admin/admin-ajax.php(207): do_action() 5 {main}

    thrown in /plugins/website-file-changes-monitor/vendor/deliciousbrains/wp-background-processing/classes/wp-background-process.php on line 551

    • This topic was modified 5 months, 2 weeks ago by Oleksandr.
    • This topic was modified 5 months, 2 weeks ago by Oleksandr.
Viewing 4 replies - 1 through 4 (of 4 total)

  • Hello Oleksandr!

    I am really sorry to hear about this experience. Since this is my first time seeing this, I would have a few questions just to shed some light on this and create some context:

    1. Can you let me know what PHP version your site has installed and what WP Core version? Or better, can you please send us the system information file?

    This file includes information about your website and our plugin’s setup so we can better understand how it is configured. You can get the system information file from the?System Info?tab in the?Help & Contact Us?section in the plugin.

    Since this file contains sensitive info about the site, please send this to us via email, while referencing this ticket on – [email protected] – so we can further investigate.

    2. Are there any particular steps in reproducing this error? Can you please also describe if this is/was a one-time error or if it happens regularly?

    3. Some screenshots of how this affects the plugin/site would also be helpful, just to visualize the impact it actually has. (make sure you also blur/hide potential sensitive data from those images before sharing them here)

    4. Did this start to happen all of a sudden? Were there any recent changes on the site – other plugin updates / new plugin installationas, core updates,, or anything else that might have been introduced?

    Looking forward to hearing back from you on this with as many details as possible.

    Thread Starter Oleksandr

    (@track77)

    Ok. I did it – check your email

    Thank you for your ongoing patience and cooperation on this one, Oleksandr!

    As per our discussion and investigations, this was caused by the ‘FS-Poster plugin which was installed on your site, and which is using an outdated version of the BG processing library.

    Even though this will also need to be included in the FS Poster plugin from their side, we managed to create a fix for this within our plugin, which turned out to be working as expected and will also be included in the next plugin update.

    Thank you!

    Plugin Author robertabela

    (@robert681)

    Hello Oleksandr,

    Please do not forget to spare a minute to rate our plugin and support. These ratings are really helpful. Thank you in advance for your time.

    Have a good day.

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