Developers of Sympa

[Joe Vieira <address@concealed>]

3976 is the feature request ID.  my crude attempt at implementation is 
there (diff file), but like i said i've been unable to save the config 
changes, so i haven't really cleaned the code up or made it nice and 
snappy yet.


Joe


Joe Vieira wrote:
> Okay, cool. I will do that today
>
> i am going to be out of town for a week so i'm going to have to put this
> on hold for a little bit, but i'll get the feature request in at the least.
>
> Joe
>
> address@concealed wrote:
>   
> > Hi Joe -
> >
> > https://sourcesup.cru.fr/tracker/?group_id=23
> >
> > This is the feature/bug tracker for sympa -- it might be good if you added an 
> > entry for your project there.  Once you have a feature request open, you 
> > could then post your patches for the implementation.
> >
> > I have a desire to to help you out with this and think that the feature 
> > tracker would be the best place to catalogue the code changes you will 
> > perform.
> >
> > Yours Truly,
> > Charles
> >
> > On Thu, Apr 10, 2008 at 08:34:24AM -0400, Joe Vieira wrote:
> >
> >     
> > > I've already got everything needed written, i just can't SAVE the list
> > > correctly.
> > >
> > > Joe Vieira wrote:
> > >
> > >       
> > > > Olivier Sala??n wrote:
> > > >
> > > >
> > > >         
> > > > > Hi Joe,
> > > > >
> > > > > Joe Vieira a ??crit :
> > > > >
> > > > >
> > > > >
> > > > >           
> > > > > > I am also making a few changes to support administrative functions,
> > > > > > for import from our old list server, and for automation from our
> > > > > > automated systems.
> > > > > > Yes, i am modifying sympasoap.pm, i've already modified the WSDL and
> > > > > > created a few of the other functions i need, everything else is
> > > > > > working fine just getting the actual list to save the changes has been
> > > > > > annoying.
> > > > > >
> > > > > >
> > > > > >
> > > > > >             
> > > > > If many sympa users have the same needs, it's too bad everybody are
> > > > > doing the same customizations on their own.
> > > > > The ideal would be that you describe your context and needs in a very
> > > > > precise way. Producing such a specification would motivate us to write
> > > > > the code.
> > > > >
> > > > >
> > > > >
> > > > >           
> > > > I've no problem writing the code to do it myself and submitting it back
> > > > into the project, which is why i am looking for pointers on HOW to save
> > > > the config back.
> > > >
> > > >
> > > >         
> > > > > > &admin::update_list okay, i'll give that function a shot! thanks a ton
> > > > > > for your help!
> > > > > >
> > > > > > do you know if &admin::update_list can modify any of the LDAP include
> > > > > > stuff? i am assuming it can't because it's in the admin module...so a
> > > > > > point in the right direction there would be helpful also =).
> > > > > >
> > > > > >
> > > > > >
> > > > > >             
> > > > > Actualy the &admin::update_list() subroutine is not the appropriate way
> > > > > to save a list config on disk, because it is very much related to list
> > > > > famillies and you probably don't use this feature.
> > > > >
> > > > >
> > > > >
> > > > >           
> > > > So what function IS appropriate?  or what was i doing wrong using
> > > > &List::save_config()?
> > > >
> > > >
> > > > Thanks a lot!
> > > > Joe
> > > >
> > > >
> > > >         
>
>