[Kim]

Any update on this?

[Kim]

This reply is private.

[Kim]

This reply is private.

[Kim]

Hi Barry, thanks for the update. Good to hear you’re working on it. However, we are frankly quite surprised it is taking so long. This is not merely a bug but the whole functionality which we paid $89 for does simply not work as advertised. It’s been 1.5 months now and we still can’t launch due to this. We think a partial refund would be appropriate by now as we wait for the fix.

[Kim]

We don’t see this particular error anymore but a new one has popped up which generates A LOT of entries (every 2 seconds once it starts):
[18-Jun-2017 17:07:25 UTC] PHP Notice: Trying to get property of non-object in /home/futuresu/public_html/eade/live/wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/API/Import.php on line 91
We tried deleting and recreating all imports, to no avail. The initial import always works, subsequent ones do not.

[Kim]

Thanks for the update, unfortunately it’s still not working for us. While it seems the imports are now being executed properly (with some even succeeding), most of them say “Import failed”. Here is an excerpt from the event log:

2017-06-13 08:00:08	No Records over retention limit, skipped pruning expired	debug	aggregator
2017-06-13 08:00:08	No Records Pending, skipped Fetching from service	debug	aggregator
2017-06-13 08:00:08	Record (4850) skipped, not scheduled time	debug	aggregator
2017-06-13 08:00:08	Record (4848) skipped, not scheduled time	debug	aggregator

Not sure what is meant by “not scheduled time”, as all imports of course have a scheduled time to run.

Should I create a new issue for this?

[Kim]

Sorry, I somehow stopped receiving email notifications for this thread after Elza’s message (not even in spam).

Here are the WP_DEBUG messages from debug.log:

[31-May-2017 11:17:00 UTC] PHP Notice:  Undefined index: disabled in /wp-content/plugins/events-calendar-pro/src/Tribe/Main.php on line 216
[31-May-2017 11:17:00 UTC] PHP Warning:  in_array() expects parameter 2 to be array, null given in /wp-content/plugins/events-calendar-pro/src/Tribe/Main.php on line 239
[31-May-2017 11:17:00 UTC] PHP Warning:  in_array() expects parameter 2 to be array, null given in /wp-content/plugins/events-calendar-pro/src/Tribe/Main.php on line 239
[01-Jun-2017 08:21:41 UTC] PHP Notice:  Undefined index: queue in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Queue.php on line 131
[01-Jun-2017 08:21:49 UTC] PHP Notice:  Undefined index: queue in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Queue.php on line 131
[01-Jun-2017 08:27:00 UTC] PHP Notice:  Undefined index: queue in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Queue.php on line 131
[01-Jun-2017 08:31:39 UTC] PHP Notice:  Undefined index: queue in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Queue.php on line 131
[01-Jun-2017 08:32:09 UTC] PHP Notice:  Undefined index: queue in /wp-content/plugins/the-events-calendar/src/Tribe/Aggregator/Record/Queue.php on line 131

(I have stripped the first part of the path, so it can be shared publicly)

While I share other commentator’s frustration about such a serious bug right after purchasing, it’s good to hear you are working on resolving it. I’d rather have it well-tested then shelling out a hotfix which breaks other things.

[Kim]

This reply is private.

[Author]

Posts