[Mailman-Users] Changing the default archive pages
Rodriguez Gomez Pedro
Pedro.Rodriguez at emea.eu.int
Thu Feb 12 17:50:07 CET 2004
Thanks! it works now
Pedro Rodriguez Gomez
From: Richard Barrett [mailto:r.barrett at openinfo.co.uk]
Sent: 12 February 2004 16:32
To: Rodriguez Gomez Pedro
Cc: mailman-users at python.org
Subject: Re: [Mailman-Users] Changing the default archive pages
On 12 Feb 2004, at 16:06, Rodriguez Gomez Pedro wrote:
> Sorry, I forgot to say that I also tried to put the files in
> "$prefix/archives/private/test" and it didn't work either.
> Pedro Rodriguez Gomez
> -----Original Message-----
> From: Rodriguez Gomez Pedro
> Sent: 12 February 2004 16:02
> To: 'mailman-users at python.org'
> Subject: Changing the default archive pages
> I am working with Mailman 2.1.3 and my problem is changing the "look
> and feel" of the Archive pages of every list in my system.
> I know that there is a folder with default templates
> "$prefix/template/<language>/", and inside this folder the files
> "article.html", "archidxfoot.html", "archidxhead.html" , ... that
> contain the default "look and feel" of the archive pages. But if I
> copy (and then change) these files into
> "$prefix/lists/test/<language>", being "test" a new list with no
> messages so far, and then I send a first message to the list, nothing
> happens, I mean nothing but the archives are generated as always. If I
> do the same proccess, but changing the files directly in
> "$prefix/template/<language>/" the result is the same.
> Am I doing something wrong?
For performance reasons the templates are cached by the various
qrunners while they are running. As a consquence you need to use
mailmanctl restart after changing templates so that the qrunners will
pick up the new versions from disk and incorporate them in to into
The following information quoted from $prefix/Mailman/Uils.py may be of
use to you:
# When looking for a template in a specific language, there are 4
# that are searched, in this order:
# 1. the list-specific language directory
# 2. the domain-specific language directory
# 3. the site-wide language directory
# 4. the global default language directory
# The first match found stops the search. In this way, you can
# templates at the desired level, or, if you use only the default
# templates, you don't need to change anything. You should never
# files in the templates/<language> subdirectory, since Mailman will
# overwrite these when you upgrade. That's what the templates/site
# language directories are for.
# A further complication is that the language to search for is
# by both the `lang' and `mlist' arguments. The search order there
# that if lang is given, then the 4 locations above are searched,
# substituting lang for <language>. If no match is found, and
# given, then the 4 locations are searched using the list's
# language. After that, the server default language is used for
# <language>. If that still doesn't yield a template, then the
# distribution's English language template is used as an ultimate
# fallback. If that's missing you've got big problems. ;)
Note that you should not make changes to templates in the
$prefix/Mailman/templates directory as those changes will be lost when
you next upgrade Mailman; put your changed templates under
$prefix/templates/site/ if, for instance, you want them to apply to all
lists on your server in place of the defaults.
> Pedro Rodriguez Gomez
> This e-mail has been scanned for all viruses by EMEA.
Richard Barrett http://www.openinfo.co.uk
This e-mail has been scanned for all viruses by EMEA.
More information about the Mailman-Users