Error in Recurrence meta strings

[Christal Glover]

I noticed the following error in our logs

Warning: sprintf(): Too few arguments in …/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence_Meta.php on line 1702

I’ve tracked it down to the string for ‘custom-monthly-on-diff-time’ being misformatted:

An event every %1$s month(s) on %2$s that begins at %3$s and lasts %4$s day(s) and %5$s hour(s), the last of which will begin on %7$s

The last substitution in the string is indexed with 7, but it should probably be 6. You can see the issues this causes in the admin and on the front end

I changed it to 6 and it fixed the issue in the admin but there’s still an issue on the front end. Many of the arguments passed into sprintf are null. See screen shots taken after changing the last substitution to %6$s

[George]

Hey @Christal,

I’m sorry about these issues – I noticed in your “System Information” that you’re using Events Calendar Pro is at version 3.12.2. We’re currently at 3.12.5, and this error should be fixed in 3.12.5

If you update, does the issue persist?

Thanks!
George

[Christal Glover]

George,

I’ve updated to 3.12.5 and the problem persists

[Christal Glover]

George,

Here’s a better screen shot of the options I am using for the recurrence

[George]

Thank you for this @Christal!

We did fix this and for some reason didn’t package it correctly in the 3.12.5 fix, and will have it actually fixed in the next update. Really sorry about that! 🙁

[Gabe Frederito]

I am having this issue as well and running the latest version 3.12.6. Where can I get the fix or are we waiting for a new release?

http://kneedeepbrewing.com/tap-room/

Thanks
gabe

[George]

Hey Gabe,

That is odd – I cannot recreate this issue. Hmmm…can you share your system information with us? Here’s how → https://theeventscalendar.com/knowledgebase/sharing-sys-info/

Cheers,
George

[Gabe Frederito]

This reply is private.

[George]

Thanks for sharing this information!

I don’t see anything outright problematic; I will take another look into our code to see about this – maybe the code-merge for this fix isn’t happening until the next release.

In that event, please stay tuned to releases because this is a ticketed bugfix that we have coming in the 4.0 release at the latest.

I’m sorry about the trouble here!

Cheers,
George

[Author]

Posts