Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to propagate reminders for a google calendar event created via the gdata python api?
    primarykey
    data
    text
    <p>I'm working on a python app that uses the gdata to programmatically create and mantain a calendar for groups of people. <strong>Everything works OK, except for the reminders in shared calendars</strong>.</p> <p>Some context: when you create a new project, a google calendar is created for it under your name. And when you invite collaborators, that same calendar is shared with them. That way, when you create tasks everybody can see them in their calendars. All of this is implemented and works fine. </p> <p>Now, I wanted people to get reminded a day before about pending tasks. So I did this:</p> <pre><code>event = CalendarEventEntry() #more stuff with the event, such as setting start and end times... for w in event.when: w.reminder.append(Reminder(days=1, method="email")) </code></pre> <p>The thing is, <strong>the reminder is only being sent to the owner of the calendar</strong>, not the other people with whom it's shared. </p> <p>I've found info about google calendar stating that it should <a href="http://www.google.com/support/forum/p/Calendar/thread?tid=3e63cca8af3aaba7&amp;hl=en" rel="noreferrer">be done manually in each user's settings</a>, which is a solution I don't like, as the whole point of my app is updating your calendar programmatically; I've also read that it could be solved by creating groups and using group calendars, but that would mean (a) my existing users wouldn't be benefited and (b) probably significant overhead, which I would happily undertake if there's no decent solution for this particular issue.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload