[terrizsolo]

Ah! Didn’t know it would automatically update when there is a fix. Perfect 🙂

[terrizsolo]

Understood, and thank you for looking into it!

Can we keep this open until it is resolved (one way or the other) please?

[terrizsolo]

Fabulous!

[terrizsolo]

No worries, I know you are making a lot of changes and chasing a lot of little bugs! Miscommunication happens.

Delighted that I will get notified; not knowing when the feature would be reinstated was what brought me searching tonight. Now I don’t have to check back 😉

Thanks!

[terrizsolo]

To clarify, I’m not seeing it in the ADMIN area. I haven’t tried to display it on the front end yet (I took it out, pending resolution of this issue.)

[terrizsolo]

Waaaait – in, the support thread referenced above:

• Nico indicated it was intentional but would be put back in a future release, and
• Geoff announced that the issue was indeed resolved in 3.12.3

Has this stance changed?

Has the issue actually been resolved? Because I’m not seeing the recurrence text box in my installation, and I have EC Pro 3.12.4.

Please advise.

[terrizsolo]

ok

[terrizsolo]

This reply is private.

[terrizsolo]

Overnight, I got 4 errors.

I screwed up with the new class I put in – I put in a recurrence rule of every day, but forgot to change the second setting to Never. Duh. I’ve done that now. I’ll watch what happens overnight.

With the other class, it still created an exclusion on its own. So this may just be an issue with legacy events.

I’ll send you a backup for today. Not sure what happened to the link but it was probably operator error 😉

[terrizsolo]

This reply is private.

[terrizsolo]

Hi Brian,

Here are the settings for one of the events (you can see the three exclusions auto-generated so far):

I edited these to stop the existing recurrence, but add a new one starting today (I set the exclusions to None to get rid of them):

———————-

For the second class, I created an entirely new event, and made the old one a draft.

I’ll see what happens. And I’ll provide you the link to the database next…

Peace,
Terri Z

[terrizsolo]

I’m getting the error recorded in the log still 🙁

A few observations:

• It seems that each night, another exclusion is added auto-magically to each of our two daily-recurring events. The exclusion is for the previous day.
• Also overnight, on the first night after all previous exclusions were removed manually, two errors are logged. I’m going to guess that it is one for each of our two recurring events.
• On the second night, 2 additional exclusions are added, one to each class (total of 4) and 4 errors are logged. Perhaps that connection can provide some insight.
• At this point, I’d suggest that we could just recreate those two recurring classes.
• Or, if there is the possibility that others may see this later, I’m happy to provide a backup copy of our database. I will warn you that it is large, >6000 posts. Just let me know how I could send it to you.
• I know you are trying to recreate the issue. These two events were originally created in January 2015 under the 3.9.x version. It might be necessary to start with a (daily) recurring event created in that environment. Then upgrade to 3.10 and then 3.11 (not sure if it makes a difference to skip versions.) Just my $0.02, worth what paid for 😉

Hope this helps somehow. Please let me know what you want me to do next!

Peace,
Terri Z

[terrizsolo]

Hi Brian,

I’ve updated to 3.12.4 as requested. I also went into my two recurring events and removed all of the exclusions that had “auto-created” themselves. And I’ve deleted the error_log so it is starting from scratch again.

I will let you know what happens! And am happy to provide whatever you need 🙂 Hopefully it will also help someone else!

[terrizsolo]

Hi George,

I switched to twenty twelve theme and save Permalink settings (without making changes), as you suggested.

No joy 🙁 Exact same behavior…

[terrizsolo]

Hi Brian,

So sorry for the delay in responding – I thought I had replied but I must not have hit submit!

I’m still seeing the error:
[08-Oct-2015 05:30:05 UTC] PHP Warning: strtotime() expects parameter 1 to be string, array given in /home/soloentr/public_html/blog/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence_Meta.php on line 1060

Here’s an interesting twist: For the 8th, there were two error messages in the error log file. Ditto for the 9th. (i.e., a total of 4 messages, 2 dated 08-Oct and 2 dated 09-Oct). On the 10th, four with the 10-Oct date stamp (8 total). On the 11th, six. Each day since then there are two more errors with that date stamp than the previous day.

This sure is a squirrel-y error!

[Author]

Posts