Uncaught ArgumentCountError: Too few arguments to function WC_Emails::email_head

I posted the fix here: https://www.ads-software.com/support/topic/woocommerce-4-9-0/

There are two ways to fix this.

Method 1) Change “public function email_header( $email_heading, $email )” in \public_html\wp-content\plugins\woocommerce\includes\class-wc-emails.php Doing the fix here is only temporary because once there is another woocommerce update this file may be updated and the change will be reverted.

Change this at line 269:

	public function email_header( $email_heading, $email ) {
		wc_get_template(
			'emails/email-header.php',
			array(
				'email_heading' => $email_heading,
				'email'         => $email,
			)
		);
	}

To the old function before the woocommerce update:

	public function email_header( $email_heading ) {
		wc_get_template( 'emails/email-header.php', array( 'email_heading' => $email_heading ) );
	}

Method 2) This changes code only in the (Quotes for woocommerce) plugin, but there’s a annoying few steps because there’s something else that is broken, custom email templates are saved to a incorrect folder.

Step 1: Go into WP-Admin – Woocommerce > Settings > Emails

Step 2: Click on “New Quote Request Sent” to Manage

Step 3: Go down to HTML and click on (Copy file to theme) –
This should copy the file to
\public_html\wp-content\themes\your-theme\quotes-for-wc\emails\new-request-sent-customer.php

but it instead copies it to
\public_html\wp-content\themes\your-theme\woocommerce\emails\new-request-sent-customer.php

If this happens you have to manually move new-request-sent-customer.php to \public_html\wp-content\themes\your-theme\quotes-for-wc\emails\new-request-sent-customer.php

Step 4: Open \public_html\wp-content\themes\your-theme\quotes-for-wc\emails\new-request-sent-customer.php and change following:

Line 15:
do_action( 'woocommerce_email_header', $email_heading );

to

do_action( 'woocommerce_email_header', $email_heading, $email );

Hi all,

I apologize. Will be releasing an update with the fix soon.

Thanks,
Pinal

Hi Steve,

An update has been released (v1.7.1) fixing this issue. Once again, please accept apologies for the issues faced.

Thanks,
Pinal