• Fatal error: Uncaught TypeError: hash_hmac() expects parameter 3 to be string, bool given in /XXX/app/plugins/woocommerce/src/Internal/Admin/Logging/FileV2/File.php:192 Stack trace: #0 /XXX/app/plugins/woocommerce/src/Internal/Admin/Logging/FileV2/File.php(192): hash_hmac(‘md5’, ‘woo-vipps-2024-…’, false) #1 /XXX/app/plugins/woocommerce/src/Internal/Admin/Logging/FileV2/FileController.php(148): Automattic\WooCommerce\Internal\Admin\Logging\FileV2\File::generate_hash(‘woo-vipps-2024-…’) #2 /XXX/app/plugins/woocommerce/src/Internal/Admin/Logging/FileV2/FileController.php(131): Automattic\WooCommerce\Internal\Admin\Logging\FileV2\FileController->generate_filename(‘woo-vipps’, 1721135411) #3 /XXX/app/plugins/woocommerce/src/Internal/Admin/Logging/LogHandlerFileV2.php(60): Automattic\WooCommerce\Internal\Admin\Logging\FileV2\FileController->write_to_file(‘woo-vipps’, ‘2024-07-16T13:1…’, 1721135411) #4 /home/G/grefsen1 in /XXX/app/plugins/woocommerce/src/Internal/Admin/Logging/FileV2/File.php on line 192

Viewing 1 replies (of 1 total)
  • Plugin Author Iver Odin Kvello

    (@iverok)

    That’s extremely weird; this is an error from WooCommerce itself, not the Vipps plugin – it seems it crashes when trying to create a log file for the Vipps plugin. The code itself is this:

            $key = Constants::get_constant( 'AUTH_SALT' ) ?? 'wc-logs';

    return hash_hmac( 'md5', $file_id, $key );

    As you can see in your error message, the $key is false here, which causes the fatal error – but AUTH_SALT should be defined in your wp-config.php file, which pretty much has to be loaded for anything to work. Can you check your wp-config file just to verify that this constant hasn’t been deleted or anything like that?

    Also, when you say “After update”, is this a recurring problem now, or did it occur once when updating or similar?

Viewing 1 replies (of 1 total)

The topic ‘Fatal error after update’ is closed to new replies.