[Mailman-Users] Custom Pages

[Janice Boothe]

Yes I do mean that.  I used confirm.html since that is the naming convention used to create custom pages for much of the other IO of Mailman.

It seems rather odd and extremely limiting that Mailman functiuons as you describe in regards to confirm.  Most of the other pages are customizable (listinfo, etc), why in the world would the programmers make such a choice to not allow site owners to customize the confirm page?  Is this something that can be fixed in future releases as it should not be very hard to do?  While I do like very much the functionality of Mailman, the default interface leaves a whole lot to be desired and lead to a very unprofessional look and feel when added to a site.


--- On Thu, 5/30/13, Mark Sapiro <mark at msapiro.net> wrote:

From: Mark Sapiro <mark at msapiro.net>
Subject: Re: [Mailman-Users] Custom Pages
To: "Janice Boothe" <nursejanice at yahoo.com>
Cc: mailman-users at python.org
Date: Thursday, May 30, 2013, 11:36 PM

On 05/30/2013 08:55 PM, Janice Boothe wrote:
> I am writing some custom mailman pages top fit the theme of my site.  I am stumped on setting up a custom confirm.html page.  Please advise how I do this.


I'm not sure what you mean by confirm.html. If you mean the results of
going to a URL like
<http://www.example.com/mailman/confirm/list_name/some_string>, those
results are all built on the fly by the Mailman/Cgi/confirm.py script.

There is a very limited control of color. See the section "Web UI
defaults" in Mailman/Defaults.py for documentation. Beyond that any
customization has to be done in the confirm.py module itself or in
methods in Mailman/htmlformat.py.

Note that it is fairly simple to add a reference to a css style sheet to
the Document.Format() method. See
<http://mail.python.org/pipermail/mailman-users/2008-March/060881.html>.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan