I just purchased the iCal sync and installed but I am having a little trouble configuring the feed to sync. So a couple questions.
- Is the URL for the Google feed the same as the URL for the ics link?
- Is that URL what gets put in the source box if not what gets put there.
Also the documentation says the instructions for getting the feed URL is at the bottom of the page but it is missing not there.
Finally was trying to access my profile to make a change but all I get is dialog box asking for login. When I enter my login info for this site it just pops the dialog up again asking for the same
Thanks
A Daley
Yes, it is the ics link. You’ll want to use the private link unless you have made the calendar public. And yes, that URL is entered into the source box.
Apologies for the error in the documentation. You find instructions on obtaining the iCal feed URL for a google calendar on this page: http://docs.wp-event-organiser.com/quick-start/importing-an-ical-feed-from-google-2/
Regarding the profile, you should be able to make changes to your profile at this url: http://wp-event-organiser.com/account/
Stephen Harris
Thanks for the quick response. Whenever I try to fetch for the first time I get an unknown error message. I tired with several different calendar ics links. I am running WP 4.42 with buddypress 2.5 BTW
Any thoughts?
I previously did a manual ics import when I was testing. Should I delete those events before syncing.
-
This reply was modified 8 years, 8 months ago by A Daley.
A Daley
Should I delete those events before syncing
Yes – but it shouldn’t stop iCal sync from working.
What iCal url are you using?
Stephen Harris
I deleted the old import and tried again and it seemed to have worked. I suspect the error message might be a process timeout. I will try to increase the limit and see if that changes.
A Daley
A Daley
Thanks, I’ve identified a probable cause. The feed contains events without a summary, and such events (since a recent update) will trigger a PHP warnings. There’ll be update to fix this shortly.
In the mean time, disabling PHP warnings will fix this problem – the issue is that the PHP warnings being printed is corrupting the ajax response.
Stephen Harris