Warning: number_format() expects parameter 1 to be float,

[Keith O Reilly]

During the latest update.

Warning: number_format() expects parameter 1 to be float, string given in /home2/gaybarce/public_html/gayrome4u/wp-content/plugins/the-events-calendar/common/src/Tribe/Cost_Utils.php on line 110

========================
PLEASE LEAVE FOR SUPPORT
Reporting the same issue as: https://theeventscalendar.com/support/forums/topic/warning-number_format-float-to-string-in-cost_utils-php-on-line-110/

========================
PLEASE LEAVE FOR SUPPORT
Reporting the same issue as: https://theeventscalendar.com/support/forums/topic/warning-number_format-float-to-string-in-cost_utils-php-on-line-110/

[Keith O Reilly]

I did a manual update to the latest version of pro – for some reason there was son error on the automatic one.

Download failed. cURL error 61: Unrecognized content encoding type. libcurl understands deflate, gzip content encodings.

The manual update to the latest version fixed the issue.

[Keith O Reilly]

Sorry, it fixed it on one site, but the same error is occurring on another.

Warning: number_format() expects parameter 1 to be float, string given in /home2/gaybarce/public_html/gayrome4u/wp-content/plugins/the-events-calendar/common/src/Tribe/Cost_Utils.php on line 110

[Jeane Sumner]

I had this problem as well. I finally figured out some enter “free” in the event cost instead of a number. When I changed that the warning message went away.

[Andras]

Hello Keith,

Thanks for reaching out to us! I’m really sorry this bug is affecting you too.

@Jeane, thanks for chiming in and sharing your thoughts / solution. Your input in much appreciated!

Good news is that a fix has been developed and if all goes well then it should be released within a week.

If you need a workaround solution until then, then downgrading to the previous version is the fastest solution.

I am going to set the status of this ticket to “pending fix” and we will update it once the fix is released. If you have ticked the “notify” checkbox, then you’ll get an email about it.

Thanks for your patience!

Cheers,
Andras

[Jeane Sumner]

No problem, @András

I was only having an issue on one site after upgrading, the others using it were fine, so that prompted us to look at some other views. It’s how we found it was one event that was causing the error for us.

[Rough & Ready]

I also had this issue and discovered that the price was set to ‘FREE’. Once I replaced the text with a zero it fixed the problem.

[Andras]

Hi Rough & Ready, thanks for chiming in too.

The fix is scheduled to be released in a couple of days. Hang in there.

Andras

[Courtney]

Hey there Keith, Rough & Ready, and Jeanne

We’ve just released an update that should fix this bug. You can read more about it at http://m.tri.be/19tp. Please update your plugins and let us know if you are still experiencing this or if we can close out this ticket.

Note: We suggest testing updates on a staging server (https://theeventscalendar.com/knowledgebase/creating-using-wordpress-staging-site/).

Thanks
Courtney 🙂

[Keith O Reilly]

That seems to have fixed the issue, thanks!

[Barry]

Awesome 🙂

Thanks for your support and patience, everyone, while we worked on this fix.

I’ll go ahead and close this topic but of course feel free to post new ones as needed if there is anything else you need assistance with.

[Author]

Posts