Plugin logging isn't going to tell you much <never has btw> because it is
just like running perl from the shell.  All it does is tell you if it ran or
not.  The way I did it was to do a Set Fields to a 'Script' field.  Then I
passed it into the ARFPerl filter.  I could tell what I was passing in by
looking at the filter logs.  I could then run the script if I needed to by
cutting the contents of 'Script' to a temp.pl file.

Thanks,  

Sean 



-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Jarl Grøneng
Sent: Friday, May 05, 2006 12:44 PM
To: arslist@ARSLIST.ORG
Subject: Re: ARF Perl PLugin

Have you tried to enable plugin logging?

--
Jarl

On 5/5/06, Grooms, Frederick W <[EMAIL PROTECTED]> wrote:
> The Perl code.  I would like to be able to log the field values passed
into the perl code (In the filter log I can see when I set the DO field of
the actual perl code but not the values of the data passed in)
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Jarl Grøneng
> Sent: Thursday, May 04, 2006 11:47 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: ARF Perl PLugin
>
> Logging of the plugin-code or logging of the perl-code running trough the
plugin?
>
> --
> Jarl
>
> On 5/4/06, Grooms, Frederick W <[EMAIL PROTECTED]> wrote:
> > Has anyone using the ARFPerl plugin added any logging to their perl
> > code?
> >
> > Fred
>
>
____________________________________________________________________________
___
> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

Reply via email to