On 1/7/2011 7:58 AM, Lander, Scott wrote:
I don’t see anything wrong, but perhaps you might review here:
http://requesttracker.wikia.com/wiki/CustomizingWithCallbacks
Heh, I've read everything there no less than 3 times in the last
24 hours :) I suppose another time can't hurt, but IMO this
is all really poorly documented.
maybe soemthing will jump out at you that I don’t see.
Also, just to check – I don’t think the default logging is at info level
– gets a bit chatty. Is it possible you are not seeing it just because
you are not logging that level?
IN your etc/RT_SIteConfig file you should have something like: ?
Yup, all set there, as I get *other* RT syslog messages.
I even changed my $RT::Logger->info call to "crit". No dice.
I succeed with $RT::Logger->info("TESTING"); from a Scrip just
fine.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Jeff Blaine
Sent: Thursday, January 06, 2011 10:17 PM
To: [email protected]
Subject: Re: [rt-users] Communicate a message to web UI from inside Scrip?
Pulling my hair out here. Why is this callback not being
tickled? I see nothing in my logs.
RT 3.8.7
Mason cache cleared and server restarted a million times.
The call to the callback in Ticket/Display.html is:
$m->callback(
CallbackName => 'BeforeDisplay',
TicketObj => \$TicketObj,
Tickets => \$Tickets,
Actions => \...@actions,
ARGSRef => \%ARGS,
);
And my setup is:
[r...@rtdev1 Display.html]# pwd
/rt/local/html/Callbacks/MyCallbacks/Ticket/Display.html
[r...@rtdev1 Display.html]# ls -l BeforeDisplay
-rw-r--r-- 1 rt root 689 Jan 6 22:06 BeforeDisplay
[r...@rtdev1 Display.html]# cat BeforeDisplay
<%INIT>
$RT::Logger->info("In Callback/Display.html/BeforeDisplay\n");
return 1;
</%INIT>
<%ARGS>
$Actions => []
</%ARGS>
------------------------------------------------------------------------------------
This e-mail message is intended only for the personal use of the recipient(s)
named above. If you are not an intended recipient, you may not review, copy or
distribute this message. If you have received this communication in error,
please notify the Hearst Service Center ([email protected]) immediately by
email and delete the original message.
------------------------------------------------------------------------------------
