In case anyone else needs to do this and for the sake of the archives,
here's how I got it working:
I created html/Callbacks/KAF/Elements/ShowSearch/ModifySearch as
follows:
# Replace any instances of __CurrentUserEmail__ with
$session{'CurrentUser'}->EmailAddress
$Search->{'Query'} =~
Good info, thanks.
So that means to have a "My Requests" widget on the "RT At A Glance"
page, I'll have to find where the hack to turn __CurrentUser__ into
the username happens, and make it happen for my widget as well.
Seems like what I want to do should be really easy. Display a widget
Good info, thanks.
So that means to have a "My Requests" widget on the "RT At A Glance"
page, I'll have to find where the hack to turn __CurrentUser__ into
the username happens, and make it happen for my widget as well.
Seems like what I want to do should be really easy. Display a widget
What is going on is that some searches used on the front page have that
special variable in them and the components that display the search results
substitute __CurrentUser__ before passing the search to the search engine.
It would be better if search parser handled this at a lower level, but it
do
I think I might have found something weird going on. One of the
included searches uses the special string "__CurrentUser__" as a
search term. This is mapped in the Elements/ShowSearch file to be
$session{"CurrentUser"}->Id.
Now the search works properly on the front page, but if you go in
