Anyone have the RTx::BecomeUser extension working under 4.0.0 or higher?
I see right away the page and navigation menu code in the extension is
not going to work with the new RT menu system. When I comment it out,
I can get the Becomeuser.html page to load, but choosing a user and
submitting just results in it saying “Congratulations, you are now so
and so” but the next RT page you visit, you are logged out.
I was going to take a blind stab at trying to fix it, but wanted to
know if anyone else did already.
I see right away the page and navigation menu code in the extension is
not going to work with the new RT menu system. When I comment it out,
I can get the Becomeuser.html page to load, but choosing a user and
submitting just results in it saying “Congratulations, you are now so
and so” but the next RT page you visit, you are logged out.
I was going to take a blind stab at trying to fix it, but wanted to
know if anyone else did already.
It might be worth contacting the author via rt.cpan.org to see if
they’ve done any work on 4.0 compatibility.
One thing to note is that I’m not sure the module could ever work if
you’re using an ExternalAuth solution (as opposed to RT’s internal
auth or RT-Authen-ExternalAuth)
I see right away the page and navigation menu code in the extension is
not going to work with the new RT menu system. When I comment it out,
I can get the Becomeuser.html page to load, but choosing a user and
submitting just results in it saying “Congratulations, you are now so
and so” but the next RT page you visit, you are logged out.
I was going to take a blind stab at trying to fix it, but wanted to
know if anyone else did already.
Allen
Would be interested to know if you make any progress with this one -
BecomeUser was a useful debugging tool in 3.xx
Would be interested to know if you make any progress with this one -
BecomeUser was a useful debugging tool in 3.xx
I got it working today and submitted it back to the CPAN maintainer. I
will give the code to anyone who asks but maybe you want to wait first
to see if he packages it up for us properly.
What I did was install the latest 1.10_2 version of the extension that
worked fine for RT3.8, and then just hacked the files under the local
plugin directory in a running instance of RT4 until it was working
again.