Apparent bug when connecting to ICS-files
I seem to have a problem when integrating ics files. When I upload a file to a server location and set to connect Dopplr with the file, Dopplr creates to entries: one dynamic entry to the uploaded file that is automatically update when something changes, and one called "uploaded calender" that cannot be refreshed.
However, I haven't uploaded anything - I just have one ics-file sitting there and I would expect Dopplr to dynamically refresh its contents.
By also connecting to the second file, I am having the further problem of duplicate and conflicting entries.
However, I haven't uploaded anything - I just have one ics-file sitting there and I would expect Dopplr to dynamically refresh its contents.
By also connecting to the second file, I am having the further problem of duplicate and conflicting entries.
1 person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hmmm. What it looks like you've done is use iCal or something similar to publish your calendar directly from your computer to Dopplr. This has resulted in the 'uploaded calendar' entry.
Somehow, Dopplr has _also_ become subscribed to this uploaded calendar as an external calendar. This is the other calendar, the one with the refresh button.
The reason the uploaded calendar has no refresh button is that it's not needed - we automatically read it when you upload a new version. The other calendar has a refresh button because it's a subscription.
The fix here is to remove the subscription to the 'remote' calendar, and just use the uploaded calendar. Assuming that I've guessed right and you really are pushing the calendar from iCal.
1 person says
this answers the question
-
Inappropriate?Thanks Tom, you guessed right. That indeed solved the problem. Actually, I didn't realize that it works this way.
I’m satisfied
Loading Profile...




EMPLOYEE