Cannot import among Multisite calendars (Your Start Date returned no results)

[Dave Robertson]

I’m having the same (or very similar) issue reported here, where TEC Pro calendars within the same Multisite network can’t be set up to import from each other.

In my scenario, imagine a Multisite network with Sites A, B and C; Site A being the “main site”.

I can set up an iCal importer feed on Site B that pulls from Site A’s feed. This does work:

1. Visit Events page on Site A and copy the link of the “+ iCal Export” button beneath the month grid.
2. In the iCal Importer admin screen of Site B (Admin > Events > Import > iCal):
   • Import Type: Recurring Every 30 minutes
   • Source: iCal URL
   • URL: http://example.com/events/?ical=1 (trimmed off the “&tribe_display=month” part)
   • Refine Results: (left all fields blank but ‘Start Date’ defaults to today’s date)
3. Click Search. Preview of events form Site A displays beneath. Looking good
4. Click Save Recurring Import; can then proceed to run the import. Yay

Now Site C has its own calendar with its own events. I repeat the same steps in order to import Site C’s events into Site B’s calendar. This time, the iCal URL is copied from Site C and pasted into Site B’s iCal Importer.

When I click the Search button (step 3) the interface displays the error “Your Start Date returned no results. Please adjust your Start Date.” The Start Date is today and there are indeed published, future events on Site C’s calendar. Sadface.

So, while an import appears to work from the main site to a sub-site, a sub-site cannot import another sub-site’s events.

[Barry]

Hi Dave,

I can see something very similar to what you have described (the problem is a little bit wider in my own testing, but it’s still clearly a problem with iCal imports running in a multisite context).

This bug has been logged and we’ll address it as quickly as we can, however I should be upfront about the fact it’s unlikely to ship in the very next upcoming release simply owing to how far along we are in that release cycle.

Of course, we’ll try to update this support topic once we’ve got something substantive to report so as to keep you in the loop.

Thanks again for reporting this and our apologies for the inconvenience.

[Dave Robertson]

Thanks. Please keep me posted.

[Barry]

Definitely 🙂

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Leah]

Hello,

Thank you for reporting this issue. We weren’t able to get a fix for it into our upcoming release (4.1). However, please know that the problem is still on our radar and is ticketed within our system to be addressed in a future maintenance release. We’ll do our best to keep you posted when we are able to get a solution in place. Thank you for your patience while we improve and expand our plugins.

Best,
Leah

[Geoff]

Hey Dave,

Just wanted to follow up and let you know that we released version 4.1.1 last night and it included a fix for this issue. Please update to the latest version if you haven’t already and do let us know if you continue to see any issues from there. 🙂

Cheers and thanks for your patience while we worked on this!

Geoff

[Author]

Posts