RT-3.8.7 Forward message bug

Hello All,

I just upgraded my test instance of RT from 3.8.2 to 3.8.7 and while
testing found that the Forward has a peculiar behavior.
Displaying a ticket and then clicking Forward on one of the transactions
behaves correctly. But using the Forward button from the top of the
display leads to a:
Can’t call method “ContentAsMIME” on an undefined value at
/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm line 529, line 75

Looking at that spot leads me to conclude that the error is correct.
There is no ContentObj. The Reply/Comment button next the the Forward
one have an empty ContentObj when used and the ContentObj is also filled
when clicking Forward next to a transaction.

I don’t know what the correct fix will be, it could either be:
generate an empty ContentObj
don’t have the Forward button on top of the display page.

Regards,

Joop

I don’t know what the correct fix will be, it could either be:
generate an empty ContentObj
don’t have the Forward button on top of the display page.

Forward at the top of the page should be reserved for “forward the whole
ticket”, I think. Will you open a ticket for this? At the very least,
the “Forward” shouldn’t explode.

signature.asc (197 Bytes)

My coworker kevin points out to me that “Forward ticket” is just what
that link at the top of the page has done since 3.8.6 and that he tried
to reproduce your issue today, but couldn’t make it break.

So, it sounds like more details are warranted.

Best,
JesseOn Thu, Dec 17, 2009 at 09:38:33AM -0500, Jesse Vincent wrote:

I don’t know what the correct fix will be, it could either be:
generate an empty ContentObj
don’t have the Forward button on top of the display page.

Forward at the top of the page should be reserved for “forward the whole
ticket”, I think. Will you open a ticket for this? At the very least,
the “Forward” shouldn’t explode.


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Jesse Vincent wrote:

My coworker kevin points out to me that “Forward ticket” is just what
that link at the top of the page has done since 3.8.6 and that he tried
to reproduce your issue today, but couldn’t make it break.

So, it sounds like more details are warranted.

Not sure whether or not my reply made it to anyone but it turned out to
be an enduser error O:-)
(not cleaning mason-cache)

Regards,

Joop