Title: Fatal error under PHP 8.1
Last modified: February 13, 2023

---

# Fatal error under PHP 8.1

 *  [AndyHenderson](https://wordpress.org/support/users/andyhenderson/)
 * (@andyhenderson)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-under-php-8-1/)
 * I used Crontrol to investigate an issue. It helped and thanks for that.
 * I left it active and started getting repeat sequences of the following when running
   Backwpup:
 *     ```wp-block-code
       [13-Feb-2023 14:05:52 UTC] PHP Fatal error: Uncaught Error: Unknown named parameter $arg in /homepages/0/d894882115/htdocs/clickandbuilds/HaylingU3A/wp-includes/class-wp-hook.php:308
       Stack trace:
       #0 /homepages/0/d894882115/htdocs/clickandbuilds/HaylingU3A/wp-includes/class-wp-hook.php(340): WP_Hook->apply_filters('', Array)
       #1 /homepages/0/d894882115/htdocs/clickandbuilds/HaylingU3A/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
       #2 /homepages/0/d894882115/htdocs/clickandbuilds/HaylingU3A/wp-cron.php(188): do_action_ref_array('backwpup_cron', Array)
       #3 {main}
       thrown in /homepages/0/d894882115/htdocs/clickandbuilds/HaylingU3A/wp-includes/class-wp-hook.php on line 308
       ```
   
 * On inspection the call_user_func_array call is passing callback: array( [function]
   => Crontrol\pauser, [accepted_args] => 1) with arguments: array( [arg]=>restart).
 * So it looks like you are adding an action to intercept cron activity which is
   running foul of PHP.
 * Deactivating Crontrol eliminated the errors. Thought you’d want to know.
 * Andy

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [3 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-under-php-8-1/#post-16466779)
 * Thanks for the report! I’ll take a look.
 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [3 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-under-php-8-1/#post-16466855)
 * [@andyhenderson](https://wordpress.org/support/users/andyhenderson/) The stack
   trace you’ve provided is very helpful thanks, but it doesn’t show anything from
   WP Crontrol. Can you confirm that the problem definitely disappears when WP Crontrol
   isn’t active?
 * The error suggests that something is converting the arguments into named parameters(
   which happens when `call_user_func_array()` is used) but I can’t see anywhere
   specifically in WP Crontrol where that could happen.
 * I’ll carry on investigating but if you can confirm if this definitely only happens
   when WP Crontrol is active that would be appreciated.
 *  Thread Starter [AndyHenderson](https://wordpress.org/support/users/andyhenderson/)
 * (@andyhenderson)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-under-php-8-1/#post-16466963)
 * The reference is in the callback on the call that creates the error: array( [
   function] => Crontrol\pauser, [accepted_args] => 1) as reported above.
 * It doesn’t appear in the stack trace but was revealed when I caught the error
   and logged the problem parameters.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Fatal error under PHP 8.1’ is closed to new replies.

 * ![](https://ps.w.org/wp-crontrol/assets/icon.svg?rev=3539529)
 * [WP Crontrol](https://wordpress.org/plugins/wp-crontrol/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-crontrol/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-crontrol/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-crontrol/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-crontrol/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-crontrol/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [AndyHenderson](https://wordpress.org/support/users/andyhenderson/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-under-php-8-1/#post-16466963)
 * Status: not resolved