The mailing list for listmasters using Sympa

["Dean Ericksen" <address@concealed>]

 

My question from two weeks ago (below) was either too simple-minded to address or too difficult to think about. So I’ll re-define it, and hope to break the silence:

·         What does it take to create a custom page that calls specific data from expl and the db, (is it possible)? Are there any examples to work from?

·         How can I request list-specific and user-specific variables on a page that doesn’t do this by default (using [% PERL %])?

 

I recognize that I could write a page in the language of my choice (python, php, perl, etc) that does everything I want, but I’d rather stay within the sympa framework as much as possible. A lot of the “edit_list_request” data looks hard to extract discretely … or it’s possible that I’m just not familiar enough with the inner-workings of sympa… We host 800+ lists, so any wisdom would go a long way.

 

Thanks.

 

-Dean

 

Previous post:

 

    * From: "Dean Ericksen" <  address@concealed>
    * To: < address@concealed>
    * Subject: [sympa-users] Creating a shortcut page for most-used admin functions
    * Date: Fri, 2 Sep 2005 14:03:54 -0700

 

I know that our list owners use a small subset of the administrative capabilities of sympa, so I want to take the most often used functions – adding an owner, adding a subscriber, changing visibility and sending-modes, etc – and move them into a more prominent place in the UI. I’d like this to be a “best of” page that provides as much as possible in one place, removing some of the options that don’t matter (or don’t get used). I’m finding that sympa’s way of rendering the administrative pages brings specific chunks of derived data into play for a given page (I think this logic sits in “Lists.pm”). Is it possible to imagine creating a new page – something in /etc/web_tt2/ or /expl/LIST/web_tt2/ – that is able to select data to build the type of “greatest hits” admin page I describe? The page might contain the following:

 

    * Add subscriber
    * Show current visibility, and allow a change
    * Show current owners, and add another (just the email address; hard-code defaults for other values)
    * Show current moderators, and add another (just the email address; hard-code defaults for other values)
    * Who can view info, send messages, subscribe…
    * Remove subscriber (simple drop-down of subscriber email addresses)

 

The last one is optional, since it would require some re-imagining of the current method of unsubscribing.

 

So my main questions are:

 

    * What does it take to create a custom page (is it possible)?
    * How can I request list-specific and user-specific variables on a page that doesn’t do this by default (using [% PERL %])?

 

Thanks in advance.

 

-Dean

www.onenw.org