Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-06 Thread Brad Knowles
At 11:21 AM -0700 2006-09-06, Dragon wrote: > The site-wide templates for each language are located on my system in > the directory /usr/local/mailman/templates/ That's the location for the as-shipped default templates, which will get over-written on the next re-install. > These would not ha

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-06 Thread Brad Knowles
At 10:39 AM -0500 2006-09-06, David Dyer-Bennet wrote: > I didn't even know there *were* list-specific versions of that; could > you tell me where they end up if they're created? The list specific stuff would be under the /usr/local/mailman/lists directory. So, for example, it might be /usr/

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-06 Thread Dragon
Ken Winter did speak thusly: >Thanks for the responses on copying customized HTML files. You are welcome and I am surprised that this has not been discussed before. This is something that really deserves a FAQ entry. If I have time later to do so, I may work one up. If not, and somebody else has

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-06 Thread Ken Winter
Thanks for the responses on copying customized HTML files. Dragon was right about the location of customized files: /usr/local/mailman/lists///. Alas, I don't have the permissions to write to those dirs, so it's back to cut-and-paste on the web site. Some other comments are inserted below. ~

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-06 Thread David Dyer-Bennet
On 9/6/06, Brad Knowles <[EMAIL PROTECTED]> wrote: > The templates are stored in the filesystem, in a variety of different > places depending on whether you're talking about the standard > as-shipped language dependent versions, the standard as-shipped > language independent versions, the site-wid

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-06 Thread stephen
Brad Knowles writes: > At 2:30 PM +0900 2006-09-06, <[EMAIL PROTECTED]> wrote: > > The templates are stored in the filesystem, in a variety of different > places depending on [all kinds o' things]. > > How you would pick and choose which specific templates are to be > considered as part

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-05 Thread Brad Knowles
At 2:30 PM +0900 2006-09-06, <[EMAIL PROTECTED]> wrote: > > > 1. Is there some way to get config_list to do this? > > > > Not that I know of, at least not without making source-code level > > changes to the tool. > > This really ought to be fixed. I don't know if the templates are even > s

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-05 Thread stephen
Brad Knowles writes: > So far as I know, the config_list tool only captures those items > which are stored in the Python pickle which contains what Mailman > thinks of as the list configuration items. Kinda miserly of it, isn't it? > > 1. Is there some way to get config_list to do this?

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-05 Thread Dragon
Brad Knowles sent the message below at 15:07 9/5/2006: >At 5:41 PM -0400 2006-09-05, Ken Winter wrote: > > > 3. If not, is there some easier way to do it than opening the "source" and > > "target" lists in the administrator web sites and cutting-and-pasting the > > HTML from one to the other? >

Re: [Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-05 Thread Brad Knowles
At 5:41 PM -0400 2006-09-05, Ken Winter wrote: > The config_list utility doesn't include the "public HTML pages" (most > importantly for me, the "General List Information Page") as part of the > configuration that it copies from one list to another. Since I have > drastically customized my Li

[Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

2006-09-05 Thread Ken Winter
The config_list utility doesn't include the "public HTML pages" (most importantly for me, the "General List Information Page") as part of the configuration that it copies from one list to another. Since I have drastically customized my List Info Page, this rather impedes cloning my lists. So,