Error in emails

[Dani]

Hi

Hope you might be able to help.

My client has had this error msg on his emails for the last three orders.

Warning: reset() expects parameter 1 to be array, string given in /home/rutland9/public_html/wp-content/plugins/event-tickets-plus/src/Tribe/Commerce/WooCommerce/Main.php on line 575

Please, can you help?

[Geoff B.]

Good morning Simon and welcome back!

First off, I would like to apologize for the delay answering.
We are currently experiencing a higher level of requests than usual.

Please rest assured that we are working hard at correcting this situation.
We appreciate your patience while we try to normalize things.

Thank you for reaching out to us.

We are sorry to hear about those error messages showing up in your client’s emails. Yikes!
I would love to help you with this topic.

This is probably caused by one of 2 things:

1. The recent WooCommerce 3 update contained some pretty substantial changes that broke compatibility with several plugins, including ours.

   The good news is that we have quickly released Event Tickets Plus which should solve all of these issues. I would recommend upgrading to 4.4.5

2. It is possible that your installation contains some customizations for our plugins that require updating.This is usually found in either the <b>/tribe-events/</b> folder of your WordPress theme’s directory or in its <b>functions.php</b> file.

   You can do a quick test to see if the problem persists while you temporarily revert back to a default WordPress theme such as twenty-sixteen.

   Or you could simply temporarily rename the <b>/tribe-events/</b> folder of your WordPress theme’s directory to <b>/z_tribe-events/</b>

Let me know how that goes.

Best regards,
Geoff B.

[Dani]

This reply is private.

[Lars]

Hello there, I’m also getting this error, tried to solve it but can get to fix it. Is there anything else I could check to solve this? Did method 2 solved your problem @Simon?

[Cordes Owen]

Hi Everyone,

I too am getting this error and I tried looking into it a little more. I went to where the error is coming from on line 575 of that Main.php file. The code looks like this…

// Store the Optout in the Attendee, from the Order Item
if ( isset( $item['item_meta'][ self::ATTENDEE_OPTOUT_KEY ] )) {
	$optout = (bool) reset( $item['item_meta'][ self::ATTENDEE_OPTOUT_KEY ] );
} else {
	$optout = false;
}

What I noticed is that apparently $item[‘item_meta’][ self::ATTENDEE_OPTOUT_KEY ] is not an array. So, if I make sure and check that it is an array first it seems to fix the issue. The only thing is I am not entirely sure what this optout code is intended to do so I am hoping I didn’t break anything. I am usually against changing code in a plugin for the obvious issues with updating but I needed it fixed because it is on a live site. So, this is what I changed the code to and the error is at least gone.

// Store the Optout in the Attendee, from the Order Item
if ( isset( $item['item_meta'][ self::ATTENDEE_OPTOUT_KEY ] ) && is_array($item['item_meta'][ self::ATTENDEE_OPTOUT_KEY ]) ) {
	$optout = (bool) reset( $item['item_meta'][ self::ATTENDEE_OPTOUT_KEY ] );
} else {
	$optout = false;
}

Will this be fixed in the next update? Do you see any issues with the change I made?

• This reply was modified 9 years ago by Cordes Owen.

[Geoff B.]

Good evening Simon, Lars and Cordes,

After investigation it looks like this is a glitch caused by the recent WooCommerce 3 update which “breaks” the extension

We apologize for the inconvenience caused by this glitch.
We have found a solution for this.

It only needs to be tested before it is released.

The good news is that you will be contacted as soon as a fix is available.
Thank you for your patience as we see this through.

Best regards,
Geoff B.

[Brook]

Howdy Guys,

We have just issued an update to the extension which shows the ticket details within Woo emails.

https://theeventscalendar.com/extensions/add-event-and-attendee-information-to-woocommerce-order-details/

If you perform a Manual Update to the latest version which is now available, these WooCommerce 3.x errors should go away!

Simon, in the file you shared, within the mse_fieldset_update_order_meta() function I am seeing some things that I believe are also going to generate notices on your website. You will likely need to rewrite portions of that function to make it Woo 3.x compatible as well.  Basically anything that treats $item as an array is going to generate notices, it could likely be replaced Woo’s $item-get_data(). There could be more things as well, I’m not a woo expert. But I just thought I’d mention it. 🙂

Thank you all for taking the time to reach out and let us know this wasn’t working properly anymore. Please let Geoff or I know if you have any questions. Cheers!

– Brook

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts