php fatal error

  • Resolved enzocm

    (@enzocm)


    5 years ago

    Dear,

    do you know why this error below is happenning? I am asking here because on #10 it seems to be related to ewww plugin. 

    [23-May-2021 22:51:49 America/Sao_Paulo] PHP Fatal error:  Uncaught Error: Unknown named parameter $tasks_meta_id in /home/u93/domains/skinkey.com.br/public_html/wp-includes/class-wp-hook.php:292
Stack trace:
#0 /home/u93/domains/skinkey.com.br/public_html/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters()
#1 /home/u93/domains/skinkey.com.br/public_html/wp-includes/plugin.php(551): WP_Hook->do_action()
#2 /home/u93/domains/skinkey.com.br/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/actions/ActionScheduler_Action.php(22): do_action_ref_array()
#3 /home/u93/domains/skinkey.com.br/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(65): ActionScheduler_Action->execute()
#4 /home/u93/domains/skinkey.com.br/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(162): ActionScheduler_Abstract_QueueRunner->process_action()
#5 /home/u93/domains/skinkey.com.br/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(132): ActionScheduler_QueueRunner->do_batch()
#6 /home/u93/domains/skinkey.com.br/public_html/wp-includes/class-wp-hook.php(292): ActionScheduler_QueueRunner->run()
#7 /home/u93/domains/skinkey.com.br/public_html/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters()
#8 /home/u93/domains/skinkey.com.br/public_html/wp-includes/plugin.php(484): WP_Hook->do_action()
#9 /home/u93/domains/skinkey.com.br/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_AsyncRequest_QueueRunner.php(52): do_action()
#10 /home/u93/domains/skinkey.com.br/public_html/wp-content/plugins/ewww-image-optimizer/vendor/wp-async-request.php(151): ActionScheduler_AsyncRequest_QueueRunner->handle()
#11 /home/u93/domains/skinkey.com.br/public_html/wp-includes/class-wp-hook.php(292): WP_Async_Request->maybe_handle()
#12 /home/u93/domains/skinkey.com.br/public_html/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters()
#13 /home/u93/domains/skinkey.com.br/public_html/wp-includes/plugin.php(484): WP_Hook->do_action()
#14 /home/u93/domains/skinkey.com.br/public_html/wp-admin/admin-ajax.php(187): do_action()
#15 {main}
  thrown in /home/u93/domains/skinkey.com.br/public_html/wp-includes/class-wp-hook.php on line 292

    Thanks a lot

    • This topic was modified 5 years ago by enzocm.
Viewing 1 replies (of 1 total)
  • Plugin Author Shane Bishop

    (@nosilver4u)

    5 years ago

    Hi @enzocm, that’s a great question. It took me a minute to realize what was going on also, but after checking that class, I realized it’s simply a matter of EWWW IO and WooCommerce using the exact same WP_Async_Request class for their async/background task processing.
    Since EWWW IO loads first, our “version” of WP_Async_Request gets loaded first, and then their ActionScheduler_AsyncRequest_QueueRunner class extends our version instead of their own, which is the expected design for such things.

    I double-checked that the classes are interchangeable, so there will be no conflicts from such a scenario. The bug then is somewhere in WooCommerce with whatever background task is attempting to run there.

Viewing 1 replies (of 1 total)

The topic ‘php fatal error’ is closed to new replies.