Getting this: Warning: max(): Array…

[ridinggravel]

I’m getting the following error on some events after installing the latest update:

“Warning: max(): Array must contain at least one element in /home/content/p3pnexwpnas07_data01/36/2533636/html/wp-content/plugins/the-events-calendar/src/Tribe/Cost_Utils.php on line 296

Warning: array_merge(): Argument #1 is not an array in /home/content/p3pnexwpnas07_data01/36/2533636/html/wp-content/plugins/the-events-calendar/src/Tribe/Cost_Utils.php on line 307

Warning: Invalid argument supplied for foreach() in /home/content/p3pnexwpnas07_data01/36/2533636/html/wp-content/plugins/the-events-calendar/src/Tribe/Cost_Utils.php on line 309”

When I add a new event, it seems to work. I’ve deactivated all plugins and it’s still happening. Only to some events. What’s happening here? Please help.

[Josh]

Hey Ben,

Thanks for reaching out to us!

On initial view of those warnings, my first assumption would be that there is a customization that exists (possibly within your theme or another plugin) that is manipulating the cost display of the events. Are you aware of any changes that may have been made in the past in this regard?

If so, you can add those snippets here and we can take a quick look at them to see what the potential conflict could be.

Thanks!

[ridinggravel]

No customizations. I’ve tried testing other themes, with all other plugins disabled and still showing this. I’ve tried 5 totally unrelated themes and also tried from zero other plugins and added back one by one. All same – still shows that.

[Douglas]

I’m having the same problem at http://tabletalknorthwest.com/events/

[Josh]

Hey,

A couple of quick questions:

1. To verify, are you using any of the ticketing solutions ( or were they being used on the site?) or are you using the default “Price” field available with core plugin?
2. Have you tried switching to a default theme? Although no additional customizations may have been manually added, there could be some customizations built into the theme that may need to be addressed.

Thanks!

[Douglas]

In my case, I discovered that one of the site managers had entered “free” instead of “0” for an event, which caused the array errors. Correcting this caused the event to render fine.

[Josh]

Hey Douglas,

Thanks for following up here! We’re working on correcting some limitations that were created with that field in upcoming releases. Glad you were able to figure out what was causing that specific issue on your site.

Ben,

Would that be a possible solution for the events that you’re experiencing this issue with?

Thanks!

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts