Re: Default read access group for Zidestore-originating events

> > > Is there are way to set the default read access team for appointments 
> > > created by _Zidestore_. For example for events synced from a mobile 
> > > phone to OGo? Setting the default read access team for new appointments 
> > > created in the WebUI is easy with
> > >   scheduler_default_readaccessteam groupname
> > > but that doesn't seem to affect Zidestore's behavior. Have I missed some 
> > > defaults?
> > I am not perfectly sure, but I think, what ever the user has configured in 
> > the webui prefereces, will be used when uploding appointments via zidestore.
> I believe that is true since r1945, 2007-05-07
> <http://www.whitemiceconsulting.com/node/117>
> But that is write access;  I don't think there is a default for read
> access,  at least not one applied by ZideStore.   If
> "scheduler_default_readaccessteam" isn't applied you could open a bug
> report.   ZideStore's access model is based on if you write it to a team
> or personal folder.   Events created in the personal folder are personal
> and events created in a team folder have access assigned to that team.
> At least that is what I recall from when I tested it.  I don't know what
> [if anything] the Overview folder does but (IMO) applying the default
> would make sense.

Here it is in ZideStore/SoObjects/ZSAppointments/SxDavAptCreate.m -
<quote>
  /* 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"];
</quote>

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

-- 
OpenGroupware.org Users
[email protected]
http://mail.opengroupware.org/mailman/listinfo/users