Hey MJ! You'll probably want to do something like this:
<@assign request$user_vars value="<@varnames scope='user'>"> <@rows array="local$user_vars"> <@var local$user_vars[<@currow>,1]> = <@var name="<@var local$user_vars[<@currow>,1]>" scope="user" encoding="none"> </@rows> Changing the scope from user to request or domain will yield the rest of the variables. What I usually do is get all the information I want, put it in a .inc file, and include it in each of the error actions. Then, when it gets called, its generates all the information, puts into one big text variable, and passes it to a method (ie. <@callmethod object="error_object" method="Email_admin(<@var local$subject>, <@var local$message>)">) which then emails the admin user. Works pretty slick, you can do lots of different stuff with it, like include timestamp, machine name, machine specs, etc. The only downside is that you have to include it in every single error action, which is kind of a PITA, at least as far as I know. If someone knows different I'd sure like to know! Cheers, Jonah -----Original Message----- From: MJPinckard [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 3:02 PM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: Returning all variables within a scope Oh.. I already use that... I've got it set to turn debugging on for my machine (by IP address) and off for all others... but that doesn't help me in my situation. What I'm trying to do is whenever a user (no debugging) runs into a problem and activates an error trap, take a snapshot of all the variables for that user (request, user, etc.) and print that along with the location in the code/site where the error was encountered to a log file... then I can go back and review the log file for get details and hopefully track down this intermittent bug. Alan Wolfe wrote: >this code will toggle debug on or off for a user, not sure if this is >what you were looking for or not. > ><@ifempty expr="@@user$debugmode"> > <@assign user$debugmode value="forceon"> <@else> > <@purge user$debugmode> > </@if> > >this is atleast one of the methods they used at the conference (: > >----- Original Message ----- >From: "Driscoll, Kevin" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Friday, July 16, 2004 4:14 AM >Subject: RE: Witango-Talk: Returning all variables within a scope > > >Fergal, >Isn't there a variable that determines if debug is on or off? > >At the Collaboree I thought someone showed that.. > >Kevin > >-----Original Message----- >From: Fergal Donlon [mailto:[EMAIL PROTECTED] >Sent: Friday, July 16, 2004 12:51 AM >To: [EMAIL PROTECTED] >Subject: Re: Witango-Talk: Returning all variables within a scope > >Hi Maggie, > >Firstly can I suggest you download the latest production version of the >Witango Server - 5.0.1.065. There were number of issues fixed between >.062 >and .065 and some did cause crashes. > >I think Alan has correctly shown how to display the name and values of >variables in a particular scope. There is also a component on the >component zone of witango.com entitled 'Show all arguments and >variables' which also demonstrates how to do this. > >Can you look in the witangoevents.log file (located in your >configuration >directory) and see if anything is being written when the crash occurs. >If >this does not reveal anything, can you check your witango.log file. >Note also that you may want to increase the logging level (set in >witango.ini) so >that more information is returned. This will give you the ability to >see what was going on in the lead up to the crash without having debug >switched on. > >I hope this helps and if I can assist you further please do not >hesitate to contact me. > >Fergal > >Fergal Donlon >Witango Technologies, >Suite 4, Level 1, >44 Miller Street, >North Sydney, 2060 > > > >----- Original Message ----- >From: "MJPinckard" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Friday, July 16, 2004 11:10 AM >Subject: Witango-Talk: Returning all variables within a scope > > > > >>What would the syntax be to capture all the variables in a specified >>scope (e.g in the manner that the debugging prints all "request" and >>"user" variables to screen)? >> >>I'm having an intermittent problem, and I'd like to log the user's >>variables when the problem occurs, so I can identify the problem. My >>thought is to capture variables whenever the error conditions are met >>during the next few weeks (the testing period before go-live on this >>code). My testers don't normally have debugging turned on, and if I >> >> >turn > > >>debugging on and reload the screen, the intermittent problem clears, >> >> >so > > >>I can't get details. >> >>I'm looking for something along the lines of <@PURGE >> >> >scope="request">, > > >>only to print, not purge. I tried <@var scope="request"> but it didn't >>work. >> >>"Well it works for me" and "just reload, it'll go away" while >> >> >accurate, > > >>is not satisfying to my users. >> >>Thanks for your help. >> >>Maggie Pinckard >>============= >>Principal Research Associate >>Enduse Forecasting >>Lawrence Berkeley Laboratory >>[EMAIL PROTECTED] >> >> >> >_______________________________________________________________________ >_ > > >>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> >> > >_______________________________________________________________________ >_ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > >_______________________________________________________________________ >_ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > >_______________________________________________________________________ >_ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
