Most changes since 1.3.21 are web ui improvements. I’d like to hear
what people think.
-j
jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
A REAL sysadmin challenge is “resurrect five dead mailserver while so ripped
to the gills on mdma that you can’t focus on any given line of text for more
than 10 seconds continuously.”
-Nathan Mehl
Hi folks,
I’m trying to get the RT development version into a workable state, since
there are some in house feature requests for our ticketing, some of which
are added (or planned) in the development tree, and some of which don’t
make much sense outside APNIC. I’ve been following development since
1.3.18 or so, and each revision, I’ve not been able to get mail returned
from the system.
Each version reports an error in the same piece of code - line 109 of
Transaction.pm, where it calls $Scrip->ScripObj->LoadAction(). The error
message I get (after uncommenting the die handler) is
“RT::Scrip::LoadAction Unimplemented in RT::Transaction.”
Does anyone have any idea why this message is appearing? Even more
confusing, with the ACL stuff, between the “Searching for scrips” debug
message at line 96 and the LoadAction() call at line 109, two ACL queries
are being executed. The only line between the debug message and the
LoadAction() call is $PossibleScrips->Next(), and an extra debug statement
verifies that’s not doing the ACL calls.
So, somewhere, something is reporting “RT::Scrip::LoadAction” to be
unimplemented, during the call to LoadAction(). Even more curious, a
quick search for “Unimplemented” through all the RT code produces no
results.
The very first debug message in LoadAction() is also never reached, or
never output.
The Scrip in question is NotifyRegularWatchersOnCorrespond(), though
Autoreply does the same thing.
Does anyone have any idea what is going on?
bje
Hrm. I haven’t actually tested mail sending since sometime before the
alpha-1 release. The scrips system has been the next thing on my list
to overhaul once I get ACLs basically working (Once I get the mechanics in
place and fix the things they break). ACLs are basically there.
Tonight, I did the first bit of work on making watchers stuff behave,
which is the first step to working mailing. I suspect that something
got munged a bit ago. More updates as I have them.
-jOn Tue, Nov 21, 2000 at 05:28:34PM +1000, Byron Ellacott wrote:
Hi folks,
I’m trying to get the RT development version into a workable state, since
there are some in house feature requests for our ticketing, some of which
are added (or planned) in the development tree, and some of which don’t
make much sense outside APNIC. I’ve been following development since
1.3.18 or so, and each revision, I’ve not been able to get mail returned
from the system.Each version reports an error in the same piece of code - line 109 of
Transaction.pm, where it calls $Scrip->ScripObj->LoadAction(). The error
message I get (after uncommenting the die handler) is
“RT::Scrip::LoadAction Unimplemented in RT::Transaction.”Does anyone have any idea why this message is appearing? Even more
confusing, with the ACL stuff, between the “Searching for scrips” debug
message at line 96 and the LoadAction() call at line 109, two ACL queries
are being executed. The only line between the debug message and the
LoadAction() call is $PossibleScrips->Next(), and an extra debug statement
verifies that’s not doing the ACL calls.So, somewhere, something is reporting “RT::Scrip::LoadAction” to be
unimplemented, during the call to LoadAction(). Even more curious, a
quick search for “Unimplemented” through all the RT code produces no
results.The very first debug message in LoadAction() is also never reached, or
never output.The Scrip in question is NotifyRegularWatchersOnCorrespond(), though
Autoreply does the same thing.Does anyone have any idea what is going on?
–
bje
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
After all, it’s not every day you meet up with an evil power
-M. Bulgakov
Found it.
I added some documentation in Scrip.pm. I didn’t end the doc
section properly so a bunch of the code got eaten. I’m about to check
in a patch that will make this all better. in fact, it just sent me an autoreply!
jOn Tue, Nov 21, 2000 at 05:28:34PM +1000, Byron Ellacott wrote:
Hi folks,
I’m trying to get the RT development version into a workable state, since
there are some in house feature requests for our ticketing, some of which
are added (or planned) in the development tree, and some of which don’t
make much sense outside APNIC. I’ve been following development since
1.3.18 or so, and each revision, I’ve not been able to get mail returned
from the system.Each version reports an error in the same piece of code - line 109 of
Transaction.pm, where it calls $Scrip->ScripObj->LoadAction(). The error
message I get (after uncommenting the die handler) is
“RT::Scrip::LoadAction Unimplemented in RT::Transaction.”Does anyone have any idea why this message is appearing? Even more
confusing, with the ACL stuff, between the “Searching for scrips” debug
message at line 96 and the LoadAction() call at line 109, two ACL queries
are being executed. The only line between the debug message and the
LoadAction() call is $PossibleScrips->Next(), and an extra debug statement
verifies that’s not doing the ACL calls.So, somewhere, something is reporting “RT::Scrip::LoadAction” to be
unimplemented, during the call to LoadAction(). Even more curious, a
quick search for “Unimplemented” through all the RT code produces no
results.The very first debug message in LoadAction() is also never reached, or
never output.The Scrip in question is NotifyRegularWatchersOnCorrespond(), though
Autoreply does the same thing.Does anyone have any idea what is going on?
–
bje
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
They’ll take my private key when they pry it from my cold dead fingers!