[tg-trunk] Re: unicode() argument 2 must be string, not None

2006-05-02 Thread Kevin Dangoor
On 5/1/06, Michele Cella [EMAIL PROTECTED] wrote: I've some fixes to try here but I'm getting this error again using latest 1.0 branch from the toolbox and also inside a quickstarted project, am I the only one? The Toolbox works for me. Is it possible you've got an old version of a widget or

[tg-trunk] Re: unicode() argument 2 must be string, not None

2006-05-02 Thread Michele Cella
Kevin Dangoor wrote: On 5/1/06, Michele Cella [EMAIL PROTECTED] wrote: I've some fixes to try here but I'm getting this error again using latest 1.0 branch from the toolbox and also inside a quickstarted project, am I the only one? The Toolbox works for me. Is it possible you've got an

[tg-trunk] Re: unicode() argument 2 must be string, not None

2006-05-02 Thread Kevin Dangoor
On 5/2/06, Michele Cella [EMAIL PROTECTED] wrote: Ok, but just to keep the timeline ordered I merged them. ;-) That's fine Regarding the unicode issue now it's all working fine, dunno why! :D It could be that I forgot to update the kid support plugin... :-/ I remember that I was getting

[tg-trunk] Re: unicode() argument 2 must be string, not None

2006-05-02 Thread Michele Cella
Kevin Dangoor wrote: I haven't seen this one myself. This is just with the default logging configuration? This could be another false alarm, it seems as you get it only if running tg-admin toolbox from outside a project dir hence without a default configuration, not a big problem... ;-)

[tg-trunk] Re: unicode() argument 2 must be string, not None

2006-05-02 Thread Kevin Dangoor
On 5/2/06, Michele Cella [EMAIL PROTECTED] wrote: This could be another false alarm, it seems as you get it only if running tg-admin toolbox from outside a project dir hence without a default configuration, not a big problem... ;-) That would still be a bug though. Do you want to Trac it?

[tg-trunk] Re: unicode() argument 2 must be string, not None

2006-05-02 Thread Michele Cella
Kevin Dangoor wrote: On 5/2/06, Michele Cella [EMAIL PROTECTED] wrote: This could be another false alarm, it seems as you get it only if running tg-admin toolbox from outside a project dir hence without a default configuration, not a big problem... ;-) That would still be a bug though.