[Evolution] Recurring meetings must be saved

Joakim Tjernlund joakim.tjernlund at transmode.se
Thu Oct 1 18:33:33 UTC 2015


On Thu, 2015-10-01 at 15:33 +0200, Milan Crha wrote:
> On Thu, 2015-10-01 at 12:50 +0000, Joakim Tjernlund wrote:
> > When I get invites to recurring meetings in evo(3.16.5) I usally have
> > to save them
> > to file before I can do anything with the meeting.
> > Attaching an example calendar.ics file which causes this behaviour.
> 
> 	Hi,
> that's correct, or at least current behaviour [1]. It's because the
> event has detached instances, which are exceptions - in some way - in
> the defined recurrence.
> 
> In this particular case, the detached instance is for today,
> 2015-10-01, where one of the changes is in the Summary property. The
> master object defines it as
>    CU-SFP/III status sync
> , while the detached instance for today defines it as
>    Cu-SFP/III status
> . Maybe the organizer wanted to rename all instances, but let his/her
> client change only this one. There are other changes too, like the
> detached instance doesn't have attendees, but it's not important.

Yes, seems like a mistake.

However, why would saving it to file and then import change anything?
If it does, evolution could do it automatically, right?

 Jocke



More information about the evolution-users mailing list