[OGo-Bugs][Bug 1979] Zidestore does not respect "scheduler_default_readaccessteam"

[bugs@opengroupware.org]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.

http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1979


awilliam@whitemice.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|helge.hess@opengroupware.org|awilliam@whitemice.org




------- Additional Comments From samuli.seppanen@tietoteema.fi  2008-05-28 14:16 -------
>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; it; rv:1.9b5) Gecko/2008050509
Firefox/3.0b5

Description of problem:
Setting "scheduler_default_readaccessteam" to "All intranet" sets the default
read-access group to "All intranet" for new events created from the WebUI.

"scheduler_default_readaccessteam" does not, however, affect events that come to
OGo via Zidestore. Zidestore-originating events are always marked as "Private".
I verified this by syncing OGo with a Nokia S60 phone (GroupDAV connector +
Funambol) and also with Cadaver by uploading new iCalendar files to

 /zidestore/dav/username/Overview 
 /zidestore/dav/username/Public/Calendar

The events were always marked as private, regardless of the
"scheduler_default_readaccessteam". It would be _very_ useful to have Zidestore
respect the default or maybe another Zidestore-specific default.


Version-Release number of selected component (if applicable):
ogo-zidestore-1.1.7-r1987.0

How reproducible:
Always

Steps to Reproduce:
1. Set "scheduler_default_readaccessteam" to "All intranet" for a user
2. Create a new OGo events aa that user through Zidestore (e.g. with Cadaver or
a mobile phone sync) to various calendars ("Overview", "Calendar",
"Public/Calendar")
2. Check the read access information for the events. They are always marked
"Private".
    

Actual Results:  All Zidestore-originating events are always "Private" (readable
by the event creator only).

Expected Results:  Zidestore should have a default to control the default read
access team or should respect the "scheduler_default_readaccessteam" default.

Additional info:

------- Additional Comments From awilliam@whitemice.org  2008-06-09 14:54 -------
This relates to the mail thread at
http://mail.opengroupware.org/pipermail/users/2008-May/018918.html

Here it is in ZideStore/SoObjects/ZSAppointments/SxDavAptCreate.m -
...
  /* read-access-group */

  if ((tmp = [[self appointment] pkeyOfGroupInContext:_ctx]) != nil)
    [self->changeSet setObject:tmp forKey:@"accessTeamId"];

  /* write access */

  tmp = [[[self appointment] container]
defaultWriteAccessListInContext:_ctx];
  if ([tmp isNotEmpty])
    [changeSet setObject:tmp forKey:@"writeAccessList"];
...

So read access, the "accessTeamId" attribute is based solely on the
folder you write too;  probably wouldn't be to hard to fix.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.