[rt-users] Problem with RT-Extension-RepliesToResolved-0.02

2013-03-06 Thread k...@rice.edu
Dear RT community,

I have installed the extension RT-Extension-RepliesToResolved-0.02
in my RT 3.8.13 installation. The scrip and scripaction are in the
database, but when I tested it on an old ticket, it recognized the
ticket as old but still re-opened it and did not create a new
ticket. Here is what was logged:

Mar  6 09:20:05 rt3 RT: A reply to resolved ticket #372109, creating a new 
ticket 
(/opt/rt3/local/plugins/RT-Extension-RepliesToResolved/lib/RT/Extension/RepliesToResolved.pm:145)
Mar  6 09:20:05 rt3 RT: rt-3.8.13-16755-1362583205-1840.372109-38...@rice.edu 
#372109/10844643 - Scrip 389 0006 On Correspond Notify Requestors and Ccs with 
template Correspondence (/opt/rt3/lib/RT/Action/SendEmail.pm:286)
Mar  6 09:20:05 rt3 RT: rt-3.8.13-16755-1362583205-1840.372109-38...@rice.edu 
No recipients found. Not sending. (/opt/rt3/lib/RT/Interface/Email.pm:382)
Mar  6 09:20:05 rt3 RT: rt-3.8.13-16755-1362583205-1053.372109-41...@rice.edu 
#372109/10844643 - Scrip 411 0007 On Correspond Notify Other Recipients with 
template Correspondence (/opt/rt3/lib/RT/Action/SendEmail.pm:286)
Mar  6 09:20:05 rt3 RT: rt-3.8.13-16755-1362583205-1053.372109-41...@rice.edu 
No recipients found. Not sending. (/opt/rt3/lib/RT/Interface/Email.pm:382)
Mar  6 09:20:06 rt3 RT: rt-3.8.13-16755-1362583205-140.372109-615...@rice.edu 
#372109/10844643 - Scrip 6159 On Correspond Notify AdminCcs 
(/opt/rt3/lib/RT/Action/SendEmail.pm:286)
Mar  6 09:20:06 rt3 RT: rt-3.8.13-16755-1362583205-140.372109-615...@rice.edu 
No recipients found. Not sending. (/opt/rt3/lib/RT/Interface/Email.pm:382)
Mar  6 09:20:06 rt3 RT: Scrip 413 IsApplicable failed: Global symbol 
$CurrentUser requires explicit package name at (eval 3920) line 20. 
(/opt/rt3/lib/RT/Condition/UserDefined.pm:65)
Mar  6 09:20:06 rt3 RT: rt-3.8.13-16755-1362583206-1020.372109-38...@rice.edu 
#372109/10844643 - Scrip 382 0362 On (Create | Correspond | AddWatcher | Queue 
Change | Owner Change | Requestor Change | Subject Change | Status Change ) 
Notify Owner (/opt/rt3/lib/RT/Action/SendEmail.pm:286)
Mar  6 09:20:06 rt3 RT: rt-3.8.13-16755-1362583206-1020.372109-38...@rice.edu 
sent  To: x...@rice.edu (/opt/rt3/lib/RT/Action/SendEmail.pm:317)
Mar  6 09:20:06 rt3 RT: Scrip 413 IsApplicable failed: Global symbol 
$CurrentUser requires explicit package name at (eval 3978) line 20. 
(/opt/rt3/lib/RT/Condition/UserDefined.pm:65)
Mar  6 09:20:06 rt3 RT: rt-3.8.13-16755-1362583206-1095.372109-38...@rice.edu 
#372109/10844644 - Scrip 382 0362 On (Create | Correspond | AddWatcher | Queue 
Change | Owner Change | Requestor Change | Subject Change | Status Change ) 
Notify Owner (/opt/rt3/lib/RT/Action/SendEmail.pm:286)
Mar  6 09:20:06 rt3 RT: rt-3.8.13-16755-1362583206-1095.372109-38...@rice.edu 
sent  To: x...@rice.edu (/opt/rt3/lib/RT/Action/SendEmail.pm:317)


Any ideas about what could be going wrong? I have applied the two patches for 
Email.pm
to our Email_local.pm file.

Regards,
Ken


-- 
RT training in Amsterdam, March 20-21: 
http://bestpractical.com/services/training.html

Help improve RT by taking our user survey: 
https://www.surveymonkey.com/s/N23JW9T


Re: [rt-users] Problem with RT-Extension-RepliesToResolved-0.02

2013-03-06 Thread Kevin Falcone
On Wed, Mar 06, 2013 at 09:43:04AM -0600, k...@rice.edu wrote:
 I have installed the extension RT-Extension-RepliesToResolved-0.02
 in my RT 3.8.13 installation. The scrip and scripaction are in the
 database, but when I tested it on an old ticket, it recognized the
 ticket as old but still re-opened it and did not create a new
 ticket. Here is what was logged:

I know I didn't test against 3.8, I'm not sure if Tim did either.

However - the Scrip part of the extension is purely to link tickets
together.  The magic to create a new ticket happens in the overrides
of Email.pm provided by the RepliesToResolved.pm file.

 Mar  6 09:20:06 rt3 RT: Scrip 413 IsApplicable failed: Global symbol 
 $CurrentUser requires explicit package name at (eval 3920) line 20. 
 (/opt/rt3/lib/RT/Condition/UserDefined.pm:65)
 Mar  6 09:20:06 rt3 RT: Scrip 413 IsApplicable failed: Global symbol 
 $CurrentUser requires explicit package name at (eval 3978) line 20. 
 (/opt/rt3/lib/RT/Condition/UserDefined.pm:65)

You appear to have a bunch of broken User Defined scrips that I don't
think belong to this extension, you may want to sort them out to avoid
muddying the water.

-kevin


pgpNYOvVXiLfm.pgp
Description: PGP signature


-- 
RT training in Amsterdam, March 20-21: 
http://bestpractical.com/services/training.html

Help improve RT by taking our user survey: 
https://www.surveymonkey.com/s/N23JW9T

Re: [rt-users] Problem with RT-Extension-RepliesToResolved-0.02

2013-03-06 Thread k...@rice.edu
On Wed, Mar 06, 2013 at 11:27:48AM -0500, Kevin Falcone wrote:
 On Wed, Mar 06, 2013 at 09:43:04AM -0600, k...@rice.edu wrote:
  I have installed the extension RT-Extension-RepliesToResolved-0.02
  in my RT 3.8.13 installation. The scrip and scripaction are in the
  database, but when I tested it on an old ticket, it recognized the
  ticket as old but still re-opened it and did not create a new
  ticket. Here is what was logged:
 
 I know I didn't test against 3.8, I'm not sure if Tim did either.
 
 However - the Scrip part of the extension is purely to link tickets
 together.  The magic to create a new ticket happens in the overrides
 of Email.pm provided by the RepliesToResolved.pm file.
 
  Mar  6 09:20:06 rt3 RT: Scrip 413 IsApplicable failed: Global symbol 
  $CurrentUser requires explicit package name at (eval 3920) line 20. 
  (/opt/rt3/lib/RT/Condition/UserDefined.pm:65)
  Mar  6 09:20:06 rt3 RT: Scrip 413 IsApplicable failed: Global symbol 
  $CurrentUser requires explicit package name at (eval 3978) line 20. 
  (/opt/rt3/lib/RT/Condition/UserDefined.pm:65)
 
 You appear to have a bunch of broken User Defined scrips that I don't
 think belong to this extension, you may want to sort them out to avoid
 muddying the water.
 
 -kevin

Hi Kevin,

That helps. I wanted to know if I had just botched a known working configuration
or blazing new ground. I will debug further. I just included all of the logs 
for the
ticket involved in case that would be at all relevant. I have it on my project 
list
to review all of the scrips.

Regards,
Ken


-- 
RT training in Amsterdam, March 20-21: 
http://bestpractical.com/services/training.html

Help improve RT by taking our user survey: 
https://www.surveymonkey.com/s/N23JW9T