[Cliff]

Awesome! 🙂

Thanks for reporting back.

[Cliff]

Please do let us know what you find out going forward. Thank you.

[Cliff]

Sorry to hear this. Could you please provide a link to the event where this happened?

[Cliff]

Hi, Chris.

Thanks for this detailed report.

Would you please provide a copy of the latest version of that plugin and then provide steps to reproduce the issue so we can attempt to replicate (and then possibly rectify) the issue?

Thank you.

[Cliff]

Derek, I checked with another team member and unfortunately we couldn’t reproduce the issue or determine a cause.

When this happens, we sometimes recommend you try to recreate the issue in a brand new WordPress installation with just our plugins and a default theme (like Twenty Seventeen). You could call this “troubleshooting in reverse”.

Sorry this causes you extra effort, but hopefully it yields some insights.

Please let us know what you find out from your additional testing.

Thank you.

[Cliff]

Good points, and I had some of the same thoughts.

We’ll get this extension released soon! I appreciate your assistance 🙂

[Cliff]

Kudos on your good sleuthing. Thanks!

We don’t have any reported bugs like this, even on PHP 7.x

Of course PHP 7+ is recommended, but we usually test with it too and don’t have any bug like this currently logged. Maybe it’s Divi that has a PHP 7 shortcoming?

Do you still get errors with PHP 7 even when our plugins are deactivated?

[Cliff]

This reply is private.

[Cliff]

I was referring to this part of the included snippet: https://gist.github.com/cliffordp/30ac2152a8264ef27235b46b7d16332d#file-functions-php-L43-L47, not anything specific to that article’s overall topic.

Is this clearer now?

[Cliff]

Sure thing!

[Cliff]

Got it. Thanks!

Please try changing your date format to YYYY-MM-DD at wp-admin > Events > Display tab > Datepicker Date Format option and see if this resolves the issue (make sure to clear site/server and browser caches).

[Cliff]

This reply is private.

[Cliff]

Here are some takeaways from reviewing your debug file (only June 1 and newer):

You must have Akismet’s debug logging enabled. Were you experiencing an issue that caused you to enable this?

[02-Jun-2017 09:08:08 UTC] PHP Notice: tribe_is_recurring_event was called incorrectly. You need to pass a post ID or use it in the loop. Please see Debugging in WordPress for more information. (This message was added in version 3.10.) in /wp-includes/functions.php on line 4138

[02-Jun-2017 20:57:29 UTC] PHP Notice: Undefined offset: 1 in /wp-admin/includes/dashboard.php on line 1227

[05-Jun-2017 14:19:35 UTC] PHP Parse error: syntax error, unexpected ‘in’ (T_STRING), expecting ‘,’ or ‘;’ in /wp-content/plugins/events-calendar-pro/src/Tribe/Asset/Ajax_Maps.php on line 29

[06-Jun-2017 10:56:57 UTC] PHP Notice: Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3884
[06-Jun-2017 10:56:57 UTC] PHP Notice: Trying to get property of non-object in /wp-includes/link-template.php on line 643

[09-Jun-2017 23:41:03 UTC] PHP Fatal error: Cannot use object of type stdClass as array in /wp-includes/http.php on line 219

[10-Jun-2017 23:15:22 UTC] PHP Notice: Undefined index: import_id in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Abstract.php on line 648

[11-Jun-2017 23:01:30 UTC] PHP Notice: Trying to get property of non-object in /wp-admin/includes/class-wp-comments-list-table.php on line 770

[11-Jun-2017 23:15:19 UTC] PHP Notice: Undefined variable: event_data in /wp-content/plugins/events-calendar-pro/src/Tribe/Countdown_Widget.php on line 36

[11-Jun-2017 23:31:42 UTC] PHP Notice: Trying to get property of non-object in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/API/Import.php on line 91 (this is the most common one I saw relating to our plugins)

[11-Jun-2017 23:36:33 UTC] PHP Fatal error: Cannot use object of type stdClass as array in /wp-includes/http.php on line 219

[12-Jun-2017 05:09:13 UTC] PHP Notice: Undefined index: queue in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Queue.php on line 136

[12-Jun-2017 08:50:37 UTC] PHP Notice: Array to string conversion in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Activity.php on line 145

[12-Jun-2017 08:50:37 UTC] PHP Warning: Illegal offset type in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Abstract.php on line 1505

[12-Jun-2017 08:50:37 UTC] PHP Notice: Object of class WP_Error could not be converted to int in /wp-includes/taxonomy.php on line 1840

[13-Jun-2017 00:08:33 UTC] PHP Notice: Undefined index: queue in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Queue.php on line 136

[13-Jun-2017 00:09:23 UTC] PHP Fatal error: Cannot use object of type stdClass as array in /wp-includes/http.php on line 219

… and likely a few more… I only got through about 10,000 lines since June 1, and that’s about 1/4 of all the debug messages since June 1. Yikes!

===

I’d suggest deleting the debug.log file, disabling Akismet’s debug mode (unless you need it on for some reason), and, now that you’re on the latest versions of everything, report back after a day of debug messages and we’ll see what is still currently/actively occurring.

Again, sorry you’re experiencing these things, and thanks for your effort toward resolving them.

[Cliff]

Sean, are you out there?

[Cliff]

Actually, I thought about this more… you can use this snippet:

https://gist.github.com/cliffordp/d420a5f952ef3b91e6db2b4104b6f28b

And then just not have these checkboxes on the Community Events form (since they’re always going to be overridden with TRUE).

Please let me know how this goes for you.

[Author]

Posts