RTFM: Can't call method "Id" on an undefined value

RT Users
1

RTFM installing was successful and in all other respects appears to be
functioning fine (same with RT).

First: click Reply to a RT ticket, select a given RTFM from the drop
down, then click “Go” to apply it. This works as expected.

Next: Click “update”.

A blank page with the following error is displayed: https://domain.com/rt/Ticket/Update.html

Can’t call method “Id” on an undefined value at /opt/rt3/local/plugins/
RT-FM/lib/RT/URI/fsck_com_rtfm.pm line 134.

However, the reply is successfully logged and any notifications emails
are sent out correctly.

Here’s the function referred to in the error:
http://pastebin.com/m2e7d01c8

Any help greatly appreciated,

james kyle

2

RTFM installing was successful and in all other respects appears to be
functioning fine (same with RT).

First: click Reply to a RT ticket, select a given RTFM from the drop
down, then click “Go” to apply it. This works as expected.

Next: Click “update”.

A blank page with the following error is displayed: https://domain.com/rt/Ticket/Update.html

Can’t call method “Id” on an undefined value at /opt/rt3/local/
plugins/
RT-FM/lib/RT/URI/fsck_com_rtfm.pm line 134.

You don’t say what versions of RT/RTFM you’re using, but this sounds
like you
have a bogus Link in the system. This should be harder to do with
rt3.8.1 and
rtfm2.4.0 but was very easy to do with earlier versions.

If you changed your $Organization setting it might also cause a problem.

Try turning on LogStackTraces and maybe you’ll be able to see what
is being passed into the uri parsing routine and failing.

-kevin

3

You don’t say what versions of RT/RTFM you’re using, but this sounds
like you
have a bogus Link in the system. This should be harder to do with
rt3.8.1 and
rtfm2.4.0 but was very easy to do with earlier versions.
My apologies, the versions are:

RT => 3.8.1
RTFM => 2.4.0

If you changed your $Organization setting it might also cause a
problem.

Try turning on LogStackTraces and maybe you’ll be able to see what
is being passed into the uri parsing routine and failing.

This did the trick. I was immediately able to see issue. It was
related to the Organization as you suspected.

Resolved.

-james