Fatal Error 2.0.24.1

  • Hi.

    The most recent update causes the same fatal error on all my websites. Rolling back to the previous version of the plugin resolves the issue.

    Please see below an example error from the site log:

    2023/09/20 06:24:57 [error] 73180#73180: *318430 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to undefined function Doofinder\WP\shell_exec() in /www/examplecom_424/public/wp-content/plugins/doofinder-for-woocommerce/includes/class-update-manager.php:205
    Stack trace: 0 [internal function]: Doofinder\WP\Update_Manager::update_020023() 1 /www/examplecom_424/public/wp-content/plugins/doofinder-for-woocommerce/includes/class-update-manager.php(43): call_user_func(Array) 2 /www/examplecom_424/public/wp-content/plugins/doofinder-for-woocommerce/doofinder-for-woocommerce.php(278): Doofinder\WP\Update_Manager::check_updates('2.0.24.1') 3 /www/examplecom_424/public/wp-includes/class-wp-hook.php(310): Doofinder\WP\Doofinder_For_WordPress::plugin_update('') 4 /www/examplecom_424/public/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(NULL, Array) 5 /www/examplecom_424/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 6 /www/examplecom_424/public/wp-includes/functions.php on line 5905PHP message: PHP Notice: Function is_singular was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /www/examplecom_424/public/wp-includes/functions.php on line 5905PHP message: PHP Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /www/examplecom_424/public/wp-includes/functions.php on line 5905PHP message: PHP Notice: Function is_search was called <strong>incorrectly</strong>.

    Kind regards,

    Simon

  • The topic ‘Fatal Error 2.0.24.1’ is closed to new replies.