Cost filter errors

[Sheila]

Client was seeing all kinds of errors and it turned out they were running a variety of versions of add-ons. Once I got them all up to the same 4.0.1, almost everything was working correctly. But I was still getting the errors listed below anytime I activated the Filter Bar. Then I noticed all the errors were with Cost. So I disabled the Cost filter and voila all is well. This is not a deal breaker for the client BUT it would be nice to have this work. And I thought maybe someone here would like to know about this issue and MIGHT even have a clue how to fix it.

Thanks…

ERRORS:
Warning: max(): Array must contain at least one element in /home/northw88/public_html/wp-content/plugins/the-events-calendar/src/Tribe/Cost_Utils.php on line 296

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

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

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

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

Warning: array_merge(): Argument #2 is not an array in /home/northw88/public_html/wp-content/plugins/the-events-calendar/src/Tribe/Cost_Utils.php on line 307

Warning: Invalid argument supplied for foreach() in /home/northw88/public_html/wp-content/plugins/the-events-calendar/src/Tribe/Cost_Utils.php on line 309

[George]

This notice unfortunately is a bug that we are working on a fix for.

What is happening is that our field now only accepts integer values, not strings. So if you enter just plain integers like 15, 120, 0, 1, etc., this error should not appear.

But if you have a string like “Free” or “Pay at door”, then this error will appear.

We are fixing this! Strings will be allowed eventually again. But that’s what this bug is for now. 🙁

I’m really sorry about the inconveniences arising from this. Please let me know if this information is helpful at all for now, and if you have any more thoughts on this matter.

Sincerely,
George

[Sheila]

Thank you George. That makes sense. And since they also have the Community add on they have a lot of users adding events in all kinds of ways so cleaning that up would be painful at best. Hopefully you’ll come out with a fix at some point.

Happy Holidays.

[George]

We’re indeed working on a fix and hoping to get it out before the holidays, though it may unfortunately come until the new year 🙁 I’m sorry about this @Sheila, but just being honest! We’re already starting to wave goodbye to some team members as they head out for the holiday break, so it’ll be a tight few weeks in terms of development and support. But we are working on this regardless!

Stay tuned to plugin updates 🙂

Cheers!
George

[Author]

Posts