On Aug 25, 2006, at 6:29 PM, Guido Sohne wrote: > On 8/16/06, Adrian Madrid <[EMAIL PROTECTED]> wrote: > How do people debug the behaviors, especially when it is running as a > plugin? I didn't find a logger object to use within the behavior > (maybe there is one, who knows?), Doing print statements only works > inside the test runs, and not under tail -f development.log, or even > the Webrick screen. I had some serious time burnt due to this, until I > resorted to using ./script/breakpointer. Sometimes too, you get an > error message trapped nicely for you by Radiant and you just want to > know what line caused it, but it's not so easy as it could be.
You can do something like: def logger ActiveRecord::Base.logger end in your behaviour to get access to a logger while testing... > > What's the secret sauce? And does Mailer work for everyone, except > maybe me? :-) It was working for me, but I had hacked it up to do some other things (like store inquiries in the database). I dont have a lot of time to look into it right now though :( Bodhi _______________________________________________ Radiant mailing list [email protected] http://lists.radiantcms.org/mailman/listinfo/radiant
