RTFM problem deleting article / CurrentUserCanSee Unimplemented

Hi everyone,

I encountered a problem with RTFM today: I am not able to delete any
article without RT throwing an error message “An internal RT error has
occurred”.

The logfile shows this:
[error]: RT::FM::Article::CurrentUserCanSee Unimplemented in
RT::Transaction.
(/usr/share/request-tracker3.8/lib/RT/Transaction_Overlay.pm line 1035)
(/usr/share/request-tracker3.8/lib/RT/Interface/Web/Handler.pm:233)

Has anyone seen this before and can point me to the direction how to fix
it? It appeared first time after the latest security update. I am using
RT 3.8.8 and RTFM 2.4.2 on Debian Squeeze.

Thanks and cheers!
Gunnar

Gunnar Gorges
Central IT Services - ZMAW
Mail: gunnar.gorges@zmaw.de
Tel.: +49 (0)40 41173 287

smime.p7s (4.58 KB)

I encountered a problem with RTFM today: I am not able to delete any
article without RT throwing an error message “An internal RT error
has occurred”.

The logfile shows this:
[error]: RT::FM::Article::CurrentUserCanSee Unimplemented in
RT::Transaction.
(/usr/share/request-tracker3.8/lib/RT/Transaction_Overlay.pm line
1035)
(/usr/share/request-tracker3.8/lib/RT/Interface/Web/Handler.pm:233)

Has anyone seen this before and can point me to the direction how to
fix it? It appeared first time after the latest security update. I
am using RT 3.8.8 and RTFM 2.4.2 on Debian Squeeze.

Since you’re running 3.8.8 from Debian, it has a number of security
fixes. The recently announced updates to RTFM include a fix to
account for these security fixes.

I believe Dom was looking for folks to test updated RTFM packages, but
I don’t have a URL handy because I’m offline.

-kevin

I encountered a problem with RTFM today: I am not able to delete any
article without RT throwing an error message “An internal RT error
has occurred”.

The logfile shows this:
[error]: RT::FM::Article::CurrentUserCanSee Unimplemented in
RT::Transaction.
(/usr/share/request-tracker3.8/lib/RT/Transaction_Overlay.pm line
1035)
(/usr/share/request-tracker3.8/lib/RT/Interface/Web/Handler.pm:233)

Has anyone seen this before and can point me to the direction how to
fix it? It appeared first time after the latest security update. I
am using RT 3.8.8 and RTFM 2.4.2 on Debian Squeeze.

Since you’re running 3.8.8 from Debian, it has a number of security
fixes. The recently announced updates to RTFM include a fix to
account for these security fixes.

I believe Dom was looking for folks to test updated RTFM packages, but
I don’t have a URL handy because I’m offline.

The URL is

http://lists.alioth.debian.org/pipermail/pkg-request-tracker-maintainers/2012-July/003280.html

I’ve just got back from a few days away so I’ll probably try and push
this out one way or another over the weekend. Testing before then
would be very welcome.

Dominic Hargreaves, Systems Development and Support Section
IT Services, University of Oxford

signature.asc (198 Bytes)

Hi Dominic,

I just was able to test the updated packages of RTFM (2.4.4) and ExternalAuth (1.1.1). Both work fine.

The problem I described below with RTFM is gone.

If you need more testing and/or more information just let me know!

Thanks and best wishes
Gunnar> On Tue, Jul 31, 2012 at 12:29:08PM -0400, Kevin Falcone wrote:

On Wed, Jul 25, 2012 at 01:30:30PM +0200, Gunnar Gorges wrote:

I encountered a problem with RTFM today: I am not able to delete any
article without RT throwing an error message “An internal RT error
has occurred”.

The logfile shows this:
[error]: RT::FM::Article::CurrentUserCanSee Unimplemented in
RT::Transaction.
(/usr/share/request-tracker3.8/lib/RT/Transaction_Overlay.pm line
1035)
(/usr/share/request-tracker3.8/lib/RT/Interface/Web/Handler.pm:233)

Has anyone seen this before and can point me to the direction how to
fix it? It appeared first time after the latest security update. I
am using RT 3.8.8 and RTFM 2.4.2 on Debian Squeeze.

Since you’re running 3.8.8 from Debian, it has a number of security
fixes. The recently announced updates to RTFM include a fix to
account for these security fixes.

I believe Dom was looking for folks to test updated RTFM packages, but
I don’t have a URL handy because I’m offline.

The URL is

[request-tracker-maintainers] [alexmv at bestpractical.com: [rt-announce] Security vulnerabilities in three commonly deployed RT extensions]

I’ve just got back from a few days away so I’ll probably try and push
this out one way or another over the weekend. Testing before then
would be very welcome.


Dominic Hargreaves, Systems Development and Support Section
IT Services, University of Oxford

Hi Dominic,

I just was able to test the updated packages of RTFM (2.4.4) and ExternalAuth (1.1.1). Both work fine.

The problem I described below with RTFM is gone.

If you need more testing and/or more information just let me know!

Hi Gunnar,

I should possibly have included more information when pointing at message
aimed originally at people familiar with the Debian package development
cycle. There’s no 2.4.4 package targetted at Debian stable; I was after
feedback on the Debian packages in our git repository[1].

http://anonscm.debian.org/gitweb/?p=pkg-request-tracker/rt-rtfm.git;a=shortlog;h=refs/heads/squeeze

Can you clarify how you installed RTFM 2.4.4 (and how you had previously
installed 2.4.2)? It’s useful feedback in any case.

Thanks,
Dominic.

Dominic Hargreaves, Systems Development and Support Section
IT Services, University of Oxford

signature.asc (198 Bytes)

I should possibly have included more information when pointing at message
aimed originally at people familiar with the Debian package development
cycle. There’s no 2.4.4 package targetted at Debian stable; I was after
feedback on the Debian packages in our git repository[1].

http://anonscm.debian.org/gitweb/?p=pkg-request-tracker/rt-rtfm.git;a=shortlog;h=refs/heads/squeeze

Can you clarify how you installed RTFM 2.4.4 (and how you had previously
installed 2.4.2)? It’s useful feedback in any case.

Well, I simply purged the RTFM 2.4.2 package (which was installed through the Debian package system) and installed 2.4.4 from the tarball. Worked without problems.
I am not familiar with the git repository but I can have a look at it anyway.

Cheers,
Gunnar