Rt2tort3: problems importing scrips

RT Users
1

Hi,

I’m currently preparing an upgrade from RT 2.0 to RT 3.8, and I’m
working through various problems with the rt2tort3 process (I’ll
post some patches to other miscellaneous problems when I’m done).

Currently I’m noticing that each time a scrip (global or per-queue)
import is attempted by dumpfile-to-rt-3.0, the warning

[Fri Oct 2 12:58:31 2009] [warning]: Use of uninitialized value $_[1] in join or string at (eval 1108) line 2. ((eval 1108):2)

is logged, and no scrip is created in the database.

This warning corresponds to the call

$so->Create(%params);

in the import_scrip subroutine in dumpfile-to-rt-3.0, and one example
%params is:

$VAR1 = {
‘ScripCondition’ => ‘On Forward’,
‘ScripAction’ => ‘Forward To Third Party’,
‘Queue’ => ‘0’,
‘Template’ => ‘Correspondence’,
‘Description’ => ‘Imported from RT 2.0’
};

Reading through RT::Scrip, RT::Record and DBIx::SearchBuilder::Record,
I can’t see what is causing this problem - the data being passed
through by RT::Scrip::Create looks fine.

Import system is Debian lenny, perl 5.10.0, RT 3.8.5, postgres 8.3.7.

Does this sound familiar to anyone who knows the RT code in more
depth than I?

Thanks,
Dominic.

Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford

2

Hi,

I’m currently preparing an upgrade from RT 2.0 to RT 3.8, and I’m
working through various problems with the rt2tort3 process (I’ll
post some patches to other miscellaneous problems when I’m done).

Currently I’m noticing that each time a scrip (global or per-queue)
import is attempted by dumpfile-to-rt-3.0, the warning

[Fri Oct 2 12:58:31 2009] [warning]: Use of uninitialized value $_[1] in join or string at (eval 1108) line 2. ((eval 1108):2)

is logged, and no scrip is created in the database.

Apologies; it does appear that the scrips are being created (must
have been caught out by transactional changes when checking earlier)
but it would still be nice to get to the bottom of the warnings.

Dominic.

Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford

3

Hi,

I’m currently preparing an upgrade from RT 2.0 to RT 3.8, and I’m
working through various problems with the rt2tort3 process (I’ll
post some patches to other miscellaneous problems when I’m done).

Currently I’m noticing that each time a scrip (global or per-queue)
import is attempted by dumpfile-to-rt-3.0, the warning

[Fri Oct 2 12:58:31 2009] [warning]: Use of uninitialized value $_[1] in join or string at (eval 1108) line 2. ((eval 1108):2)

is logged, and no scrip is created in the database.

Apologies; it does appear that the scrips are being created (must
have been caught out by transactional changes when checking earlier)
but it would still be nice to get to the bottom of the warnings.

Hello Dominic,

RT doesn’t use many evals so it’s probably in the script. Anyway,
warning looks like it was
handled by RT, so it’s possible to use LogStackTraces option to figure
out exact place.

Dominic.

–
Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.