[Systers-dev] Non-Dlist issue
kanika vats
kanika.krikan at gmail.com
Mon Aug 31 05:37:46 PDT 2009
Hello Anna!
Welcome back !! So I did the merging of both our codes,you can get the code
from orm_objectoriented branch.
On Mon, Aug 31, 2009 at 5:39 PM, Anna Granudd <anna.granudd at gmail.com>wrote:
> Hi,
> sorry for coming in a bit late in the discussion, just wanted to know how
> far you've come in solving the problems and if there is anything I can help
> clearing out? For implementing the debug mode, simply add "from
> Mailman.mm_cfg import DEBUG_MODE" at the top of the page and an if statement
> checking for the debug mode value before anything that doesn't need to be
> logged during production.
>
Yea we got to know about this during testing,actually the problem is that
even if we place DEBUG_MODE = True in mm_cfg.py then no logging occurs in
the 'info' for the new lists and if we do DEBUG_MODE = False then logging
occurs for the oldlists so the conclusion is that the presence of DEBUG_MODE
in mm_cfg.py is somehow not playing the required role,as whatever be its
value(True/False) Logging does not takes place for newlists and it always
takes place for oldlists.
Have I understood it correctly that there's a problem creating dlists with
> the dlist feature enabled? I haven't got the latest set of code, but could
> it be that the value of the radio button no longer gets read and saved? It
> should be saved in the mlist object (in mlist.dlists_enabled) when creating
> the list.
>
> Yup you have got it correctly and yes that can very well be the case,so
even if we select the Dlist Feature in the radio button then also the new
list that is created is a Non-Dlist. I hope you are able to solve these two
problems,I checked the entire code and corrected all the inconsistent parts
that were dependent on my code in DlistUtils.py.If you have any problems
feel free to contact ;>
--
Best Regards
Kanika Vats
More information about the Systers-dev
mailing list