The mailing list for listmasters using Sympa

[Olivier Salaun - CRU <address@concealed>]

Hi John,

There are actually 2 ways a template can include another template :

1. directy, as in  subrequest.us.tpl : [PARSE '/home/sympa/bin/etc/wws_templates/loginbanner.us.tpl'].    If you customize the loginbanner.us.tpl, you also have to customize templates that refer to it.
2. indirectly, via a variable, as in main.tpl : [PARSE action_template]. Then wwsympa.fcgi sets action_template variable to the appropriate template file path (ie : in the best place according to Sympa default rules, and in the current language).
   

We use (2) for some high level templates (action_template,
error_template, notice_template, title_template, menu_template,
list_menu_template, admin_menu_template) but then we use (1) for
lower-level template inclusions.

I suppose it makes sense to write this down in the reference manual...

John Dalbec wrote:
> John Dalbec
> wrote: 
> > I want to customize the loginbanner.us.tpl
> > file.  If I put the customized version into /etc/sympa/wws_templates,
> > wwsympa still loads the uncustomized version from
> > /usr/share/sympa/wws_templates.  I created the loginbanner.tpl
> > symlink.  I chowned both of them to sympa:sympa.  I restarted the web
> > server.  Is there a way to make wwsympa look in /etc/sympa first and
> > then fall back to /usr/share/sympa if the file is not found? 
> >   
>   
> Sorry, I didn't realize the loginrequest.us.pl template used an
> absolute path.  Does the parser require the use of absolute paths in
> the PARSE command? 
-- 
Olivier Salaun
Comite Reseau des Universites