Let's be honest, the RTFM answer is a bit dry, but you're right we should pay closer attention to it.
A good idea would be to identify clearly the changes in the manual - when an option is being introduced or modified or when it has been deprecated and/or replaced. That would make reading the manual more user friendly, update after update. I saw that part in recent version of the documentation, but It's less than obvious to derive from those pages that you have to create those two fields in the SQL table to be able to use the functionality. Furthermore the authentication table is provided by the application itself, so one could expect the columns to be already present - or to be part of the upgrade process as other table/columns are added/modified. In the documentation mentioned, several other fields are also optional - should they also be added to the same table? I'll give it a try. But some examples would have been nice too. Dominique On 11/08/2012, at 20:11, "Ludovic Marcotte" <[email protected]> wrote: > On 11/08/12 12:32, Dominique Dominique wrote: >> >> I second the request... My own request for info months ago got unanswered.... > You should read the documentation. Page 26 and 27 from the installation and > configuration guide. > > Just create the KindFieldName and MultipleBookingsFieldName columns in your > authentication table/view and set the values accordingly. > -- > Ludovic Marcotte > +1.514.755.3630 :: www.inverse.ca > Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence > (www.packetfence.org) -- [email protected] https://inverse.ca/sogo/lists
