just a remark: as long as i stay with the webinterface, calendar seems to be working fine but when i intermix with thunderbird actions via caldav it seems to be possible to produce inconsistent states - especially when a meeting is shifted, extended or shrinked.
 
as i'm off for the rest of this week, i will further check this next week.
 
calendar is essential for us.
 
Sent: Thursday, June 23, 2016 at 3:50 PM
From: "\"\\\"sg gs\\\"\" ([email protected])" <[email protected]>
To: [email protected]
Subject: Re: [SOGo] evaluating sogo - 2. calendar / 2
hello francis,
 
v3.1.3.20160623-1 behaves well while v3.1.3 still seems to suffer from this weakness.
 
best regards, gustav
 
 
Sent: Friday, June 17, 2016 at 9:33 PM
From: "\"Francis Lachapelle\" ([email protected])" <[email protected]>
To: [email protected]
Subject: Re: [SOGo] evaluating sogo - 2. calendar / 2
Hello sggs

> On Jun 17, 2016, at 9:36 AM, sg gs ([email protected]) <[email protected]> wrote:
>
> the same seems to be true for domo v3 demo @ sogo.nu ( http://demo.sogo.nu/SOGo/ )
>
> Sent: Friday, June 17, 2016 at 10:02 AM
> From: "\"\\\"sg gs\\\"\" ([email protected])" <[email protected]>
> To: [email protected]
> Subject: [SOGo] evaluating sogo - 2. calendar / 2
> hello again,
>
> in order to evaluate sogo v3.3.12, i created a second sogo instace using the same data (ldap,dovecot and prostgres) as the v2.3.12 instance.
>
> using v3.1.12, i am observing the following behaviour:
>
> 1. A creates a meeting and invites B
> 2. B recieves an email and accepts the meeting
> 3. A reopens the meeting and can see that B has accepted
> 4. A clicks 'Edit' and saves the meeting without changing anything
> 5. A reopens the meeting and B's accepted status has changed to 'not accepted' (?)
> 6. B did not receive any meeting-related mail and sees his own status a 'not accepted'.
>
> this works different, more useful, in v2.3.12
>
> moreover, if a resource was invited, it does not accept the invitation as it does in v2.3.12.
>
> what can i do to change this? did i miss anything?

It's a bug which I just fixed¹.

Thanks!

Francis

[1] https://github.com/inverse-inc/sogo/commit/8cc0b946e70f4a7643acfc4956a49b50c059f380
--
[email protected]
https://inverse.ca/sogo/lists
--
[email protected]
https://inverse.ca/sogo/lists

Reply via email to