View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003837||SOGo||Web Calendar||public||2016-10-12 11:11||2018-04-27 10:10|
|Platform||[Server] Linux||OS||Ubuntu||OS Version||12.04 LTS|
|Product Version||nightly v2|
|Fixed in Version||3.2.1|
|Summary||0003837: Conflict error by adding two concurent entries in a shared calendar|
We use SOGo V3.2.0 nightly build. Since a few weeks we are not able to add two entries which have conflict in shared calendar. It shows Conflict error and does not add the second entry.
|Steps To Reproduce|
Simply add a whole-day event in a shared calendar, and then try to add another entry in the same day into the same common calendar.
|Tags||No tags attached.|
Just to clarify.
The former. I have the write access to the shared calendar and want to add an event in a time slot that another event of the same calendar already covered a part or the whole.
Why there is no fix in recent updates?!
Happening here also.
I have upgraded recently from 3.1.4 version into 3.2.0
3.1.4 version showed conflict message, but allowed us to create the event anyway.
Today, I've downgraded my setup into 3.1.4 version.
As stated on my previous comment, conflict messages are shown, but SOGo still allowing me to create the event.
Is this helpful on any way?
In my case, SOGo does not allow to create any event which has conflict in a shared calendar!
On my understanding, this is clearly a regression introduced on 3.1.5 (which I didn't tested) or 3.2.0 (which is failing you and has been failing me for a couple of days)
I'll try to test 3.1.5 and see if I can narrow things a bit.
Conflicts are only handled for resources, so you're trying to invite a resource that has reach its maximum simultaneous bookings limit.
The error displayed in the Web interface has been fixed a few days ago.
Many thanks for the answer Francis.
FWIW, I am not using resources. What I do is:
Create an event on my calendar and invite a user who has appointments already created on this day and time frame.
As I said, on 3.1.4 conflicts are shown, but I can save the task anyway. On 3.2.0, I cannot do such thing.
So, should I expect this to be fixed on the 3.2.1 release? Is there any place I can check the release status and/or release dates?
Many thanks for the answer and the outstanding developing sogo
Try the latest nightly build. It has been fixed.
Indeed it is fixed on the nightly build. Thanks!
So, I guess this fix is going to be included on 3.2.1, am I right? Is there any candidate date or so?
Again, many many thanks.
|2016-10-12 11:email@example.com||New Issue|
|2016-10-13 07:02||Christian Mack||Note Added: 0010734|
|2016-10-13 07:firstname.lastname@example.org||Note Added: 0010735|
|2016-10-24 13:email@example.com||Note Added: 0010785|
|2016-10-26 12:05||pabelenda||Note Added: 0010789|
|2016-10-31 13:11||pabelenda||Note Added: 0010799|
|2016-10-31 14:firstname.lastname@example.org||Note Added: 0010800|
|2016-11-01 08:40||pabelenda||Note Added: 0010801|
|2016-11-01 16:05||francis||Note Added: 0010802|
|2016-11-01 16:17||pabelenda||Note Added: 0010803|
|2016-11-01 19:45||francis||Note Added: 0010805|
|2016-11-02 08:18||pabelenda||Note Added: 0010806|
|2016-11-02 08:39||pabelenda||Note Edited: 0010806|
|2016-11-02 10:email@example.com||Note Added: 0010807|
|2016-11-02 10:38||francis||Note Added: 0010808|
|2016-11-02 10:38||francis||Status||new => resolved|
|2016-11-02 10:38||francis||Fixed in Version||=> 3.2.1|
|2016-11-02 10:38||francis||Resolution||open => fixed|
|2016-11-02 10:38||francis||Assigned To||=> francis|