On Fri, Feb 25, 2011 at 04:37:32PM +0000, Giuseppe Sollazzo wrote: > On 25/02/11 15:28, Kevin Falcone wrote: > >It shouldn't actually require any JS hacking (or didn't when I last > >overrode this extension to do it). > > > > Hi Kevin, > thanks - I'll give it a look. > > >You have to hack search in the .pm to return extra data about the user > >and the EmailCompletion mason template to print it out. > > > >Be aware that RT considers some data to be sensitive (such as phone > >numbers) so it'll refuse to show it unless you mark it as accessible. > Uhm... how do you mean "mark"?
Check the methods in User/User_Overlay named *Accessible to get an idea, there should be docs there and in DBIx::SearchBuilder about what is going on. You'll need a LocalAccessible to declare some fields 'non admin'. > >In 4.0, this becomes 'write a custom ShowUser option' which isn't > >as flexible as I'd like it to be, but is a step forward. > > I'll check it out - however we'll stay for 3.8 for a while I guess, > but I'll start getting documentation about how to migrate.
pgpBl2XAzevk6.pgp
Description: PGP signature
