[Luke]

Yep, everything’s up to date!

I didn’t even realize that logging existed, let alone that it needed to be turned on by default, so apologies for that. I did go ahead and set it for full reporting. That will be very useful!

I’ve also attached a screenshot of the status area per your request.

As it happens, I forgot to check back in on this thread, and in the interim, three of four imports went just fine at times really early in the morning. The latest has a red exclamation error icon, and when I hover over it there’s some HTML that can be picked out if I do “Inspect Element” which indirectly leads to this:

https://theeventscalendar.com/knowledgebase/url-import-errors-event-aggregator/

Cause:
Similarly to the “Bad Data” error above this happens when the archive page EA Service is trying to fetch provides inconsistent or bad data in regards to the page number, the totals or the format.

This could be due to a communication error between EA service and the source site or due to a custom modification of The Events Calendar REST API that provides a response in a format we can read.

It also said to visit (beginning of the address truncated):

wp-admin/edit.php?post_type=tribe_events&page=tribe-common&tab=imports#tribe-field-tribe_aggregator_default_url_import_range%22

So I looked at the range and moved it from three months to one month; shouldn’t be an enormous difference since it’s a daily operation, and then in case there are server issues on either end, it’s less of an “ask” when the request gets issued.

I have this as “still need assistance” just in case I’m talking out of my butt and need clarification/correction, but please feel free to mark it resolved if we’re on the right track, and thank you for taking the time to look into this!

[Author]

Posts