On Thursday, July 31, 2003, at 10:37 pm, Ron Brogden wrote:
On July 31, 2003 01:58 pm, you wrote:There is a known bug in MM 2.1.2 (and earlier 2.1.x) for which a patch is available. This patch has been folded into the CVS and should thus appear in the next release of MM (2.1.3?) but for the moment it is applicable to 2.1.2; see: http://sourceforge.net/tracker/ index.php?func=detail&aid=730769&group_id=103&atid=100103
Hello Richard. Thanks for the tip but now I have a new problem (ain't that
always the case).
=)
I tried installing the patch but it seemed to have messed up the template
parsing (I was suddenly left with unparsed tags such as "%(meta)s"
everywhere. I quickly reverted back to the unmodified code but now it
appears that this data has been physically cached somewhere so now I have the
problem of not being able to clear out the stale cache.
Any idea where this cache is stored? My archives will shortly be useless if
I cannot catch this quickly (and a rebuild is nasty, nasty as this is a busy
server).
mailmanctl restart after making the code change. The cache is in process memory and is freshly created on demand within each process each time the mailman daemons or scripts are started. You will also need to rebuild existing mail archives using bin/arch to get the revised templates to affect existing HTML archive pages.
Arrrgh.
=)
Cheers
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
