Custom event. Frequency = Yearly, no end date – gives PHP error

[Adam]

Hi Support,

My client has eagerly awaited 3.12 for the custom recurrence patterns. Unfortunately this does not work when we specify “On the” first Friday, for example. I get a PHP error generated “Fatal error: Unsupported operand types in /homepages/32/d129692020/htdocs/wsc129692025/wp-content/plugins/events-calendar-pro/src/Tribe/Date_Series_Rules/Year.php on line 102”

In the Recurrence rules, if I don’t check the “On the” box then the recurrence populates the calender but obviously always on the same date each month which is not what the client wants, they want for example. first Friday or 2nd Wednesday.

This is really important to my client and myself that this is resolved asap.

Best regards,

Adam.

[Nico]

Hi Adam,

Thanks for reaching out to us, and sorry for any inconvenience this issue might be causing to your client 🙁

I’ve tried to reproduce this on my end but I’m not getting any errors, Can you send over a screenshot of the recurrence settings just to be sure I’m setting everything up correctly?

Also, you indicated this was tested with default WordPress theme and no other plugins active, Can you confirm that? Did you get the same error?

Hope we can make this right soon,
Best,
Nico

[Adam]

Hi Nico,

Thanks for the reply. Here is a screen shot, it was the first custom recurrence pattern I tried. I then tried a simpler one, just one month ticked and “First” “Monday” and it also failed. I noticed that the recurrence only fails when “On the” is ticked, i.e. repeats on specific day, not on specific date. If “On the” is not ticked then the recurrence works but this is not what my client wants. They want for example on “First Friday” not on say every 2nd of the month – hope that makes sense.

As for testing, as well as the actual website I have a local fresh installation of WordPress running under Xampp on Windows 10. No other plugins activated, the default theme running. The recurrence with “On the” ticked fails for both the website and my local test system. In both setups I get the same error ending in “wp-content/plugins/events-calendar-pro/src/Tribe/Date_Series_Rules/Year.php on line 102”

If you need any more info, please let me know.

Thanks for all the help, Adam.

[Nico]

Hey Adam,

Thanks for the detailed follow-up! I could reproduce this locally, so this is now logged as a Bug in our product backlog. I’m not sure of how complex the fix for this might be. Hope it’s an easy one and that we can see this fixed in the maintenance release coming out shortly.

I’ll keep you updated regarding this issue, thanks a lot for taking the time to trouble shoot this locally also 🙂

Have a great weekend,
Nico

[Adam]

Hi Nico,

I look forward to the fix. In the mean time I’m wanting to go back to the client with some news on the matter and possibly a work around. Until the maintenance release is available, would it be possible to send me a work around, maybe in the form of an updated PHP file (“wp-content/plugins/events-calendar-pro/src/Tribe/Date_Series_Rules/Year.php”, since this was the one that looked like the error was being cause in) that I could upload the site in question?

Whilst I appreciate that Modern Tribe has many customers, am I to assume that this issue will be looked at with the utmost urgency since “flexible/free-form recurring events (PRO)” is listed at the top of the features sent out in the in “Version 3.12 of The Events Calendar and add-ons has shipped!” email?

Best regards,

Adam.

[Nico]

Hi Adam,

Thanks for following up and also for taking the time to send as such a thoughtful feedback. I appreciate that!

We are actively working on this and I can confirm this has been added to the Maintenance Release scope. That means it’s coming up as soon as possible -hopefully before the end of the month. Sending you a patch for the file might not be the best solution as there other bugs with custom recurrence that needs a tweak, and it’s possible you get other errors with the patch in place.

We are aware this is an important feature to our customers, that’s why this is also top priority for us. I understand the frustration of looking forward to a feature just to find out it stills needs adjustments after the release 🙁 I sincerely hope we can see this fixed really soon.

Best,
Nico

[Geoff]

Hey there,

Just want to let you know that we just shipped an update and a patch for this issue was included. Please update and feel free to drop us a new note if you continue to bump into any issues with this. We appreciate your patience while we worked on this–thanks for your support!

Cheers,
Geoff

[Author]

Posts