I’ve got a fresh install of RT 3.2.2 on FedoraCore 3, running httpd
2.0.52-3.1, perl 5.8.5, using mod_perl. Everything works, but I’m
having trouble with turning on the ‘ShowNavigation’ feature in the
Element MyRequests (or any of the Elements for that matter).
I’ve copied MyRequests from
/var/lib/rt3/share/html/Elements/MyRequests to
/var/lib/rt3/local/html/Elements/MyRequests and changed the one line
with ShowNavigation from a ‘0’ to a ‘1’.
The main page shows up just fine when I reload it in the browser, but
when I click on the link, I get the following:
The requested URL /Order=DESC&Query=Owner = ‘Nobody’ AND ( Status = ‘new’ OR Status = ‘open’)&Rows=10&OrderBy=Created&Page=2&Format=‘id/TITLE:#’, ‘Subject/TITLE:Subject’, QueueName, ExtendedStatus, CreatedRelative, 'Take/TITLE: ’ was not found on this server.
The interesting thing is that the Link I clicked on is:
http://rt3.taec.toshiba.com/Order=DESC&Query=Owner%20%3D%20'Nobody'%20AND%20(%20Status%20%3D%20'new'%20OR%20Status%20%3D%20'open')&Rows=10&OrderBy=Created&Page=2&Format='<a%20href%3D"%2FTicket%2FDisplay.html%3Fid%3D__id__">__id__<%2Fa>%2FTITLE%3A%23'%2C%20'<a%20href%3D"%2FTicket%2FDisplay.html%3Fid%3D__id__">__Subject__<%2Fa>%2FTITLE%3ASubject'%2C%20QueueName%2C%20ExtendedStatus%2C%20CreatedRelative%2C%20'<a%20href%3D"%2FTicket%2FDisplay.html%3FAction%3DTake%26amp%3Bid%3D__id__">Take<%2Fa>%2FTITLE%3A%26nbsp%3B'%20
But the link at the top of the MyRequests section seems ot have:
http://rt3.taec.toshiba.com/Search/Results.html?Order=DESC&Query=Owner%20%3D%20'Nobody'%20AND%20(%20Status%20%3D%20'new'%20OR%20Status%20%3D%20'open')&OrderBy=Priority
So I wonder if the way the Query is put together when the
ShowNavigation is turned on is broken somewhere? Could there be an
issue with the Elements/TicketList code?
my $prev = $m->comp('/Elements/QueryString',
Query => $Query,
Format => $Format,
Rows => $Rows,
OrderBy => $OrderBy,
Order => $Order,
Page => ($Page-1));
So it looks like I need to put in some code to include the PATH to the
“/Elements/SearchResults.html?” target, to base the query upon. I see
that QueryString is just a filter to encode the arguements, but
wouldn’t they already be encoded properly, since it’s part of the RT
generated URLs?
I’m going to keep poking at this, I’ll probably come upwith a solution
about 2 minutes after I send this problem report in…
Thanks,
John
I’ve got a fresh install of RT 3.2.2 on FedoraCore 3, running httpd
2.0.52-3.1, perl 5.8.5, using mod_perl. Everything works, but I’m
having trouble with turning on the ‘ShowNavigation’ feature in the
Element MyRequests (or any of the Elements for that matter).
ShowNavigation is only designed for the main search page. It’s not
supposed to work from embedded searches.
Jesse
“Jesse” == Jesse Vincent jesse@bestpractical.com writes:
Jesse> ShowNavigation is only designed for the main search page. It’s
Jesse> not supposed to work from embedded searches.
Bummers, since it would be really nice to have it do so. Basically, I
want to change the main page to just have a single area showing all
open & new tickets, without regard to who owns them, etc.
We’re not a large shop, so splitting up the display doesn’t make sense
for us. At least not right now.
Honestly, I’m trying to get back to the simpler setup of the RT 1.0
look, which I felt was clean and simple and used screen realestate
very effectively.
Does anyone have any suggestions or examples on how to simplify the
interface? Skins anyone? grin
And the CLI tools were much better. Sure, you had to be careful how
you setup perl and the include paths, especially if you wanted to do
the work from alot of remote systems, but we had it working nicely.
I’ve played with the new CLI, but it’s not nearly as nice or polished,
I guess there isn’t as much demand nowdays. Too bad, since using the
HTTP protocol (while understandable from your point of view!) for the
CLI isn’t ideal.
But don’t get me wrong Jesse, I think this is a great tool! I just
want to keep it simple in it’s look and power, and not impose alot of
process on the trouble ticket handling setup.
John
At Friday 1/14/2005 08:38 AM, John Stoffel wrote:
Does anyone have any suggestions or examples on how to simplify the
interface? Skins anyone? grin
At MIT we’ve done some work with the home page. We’ve removed the two
ticket listings and replaced them with three sections of links to saved or
canned searches. The three sections are:
- “my” saved searches
- Group saved searches
- Global canned searches (currently two links, mapping to the standard
home page ticket listings)
The idea is that users want direct access to “their” stuff from the home
page, and using the saved search feature gives them the ability to build a
customized list of “bookmarks” to their searches, accessible from the home
page.
Steve
Stephen Turner
Senior Programmer/Analyst - Client Support Services
Information Services and Technology (IS&T)
Massachusetts Institute of Technology
sturner@mit.edu
Stephen> At MIT we’ve done some work with the home page. We’ve removed
Stephen> the two ticket listings and replaced them with three sections
Stephen> of links to saved or canned searches. The three sections are:
Stephen> 1) “my” saved searches
Stephen> 2) Group saved searches
Stephen> 3) Global canned searches (currently two links, mapping to
Stephen> the standard home page ticket listings)
That’s a great idea. I’d also like to have a better "QuickCreate"
window for adding tickets, which is what I’m not working on.
Stephen> The idea is that users want direct access to “their” stuff
Stephen> from the home page, and using the saved search feature gives
Stephen> them the ability to build a customized list of “bookmarks” to
Stephen> their searches, accessible from the home page.
Would you be willing to share some of your code, or at least the ideas
behind it so others could use it as well?
Thanks,
John
At Friday 1/14/2005 04:22 PM, John Stoffel wrote:
Stephen> At MIT we’ve done some work with the home page. We’ve removed
Stephen> the two ticket listings and replaced them with three sections
Stephen> of links to saved or canned searches. The three sections are:
Stephen> 1) “my” saved searches
Stephen> 2) Group saved searches
Stephen> 3) Global canned searches (currently two links, mapping to
Stephen> the standard home page ticket listings)
That’s a great idea. I’d also like to have a better “QuickCreate”
window for adding tickets, which is what I’m not working on.
Stephen> The idea is that users want direct access to “their” stuff
Stephen> from the home page, and using the saved search feature gives
Stephen> them the ability to build a customized list of “bookmarks” to
Stephen> their searches, accessible from the home page.
Would you be willing to share some of your code, or at least the ideas
behind it so others could use it as well?
Absolutely - I’ll try to get something up in the wiki contrib section in
the next week or so.
Steve
Stephen Turner
Senior Programmer/Analyst - Client Support Services
Information Services and Technology (IS&T)
sturner@mit.edu
At Friday 1/14/2005 04:22 PM, John Stoffel wrote:
Stephen> At MIT we’ve done some work with the home page. We’ve removed
Stephen> the two ticket listings and replaced them with three sections
Stephen> of links to saved or canned searches. The three sections are:
Stephen> 1) “my” saved searches
Stephen> 2) Group saved searches
Stephen> 3) Global canned searches (currently two links, mapping to
Stephen> the standard home page ticket listings)
That’s a great idea. I’d also like to have a better “QuickCreate”
window for adding tickets, which is what I’m not working on.
Stephen> The idea is that users want direct access to “their” stuff
Stephen> from the home page, and using the saved search feature gives
Stephen> them the ability to build a customized list of “bookmarks” to
Stephen> their searches, accessible from the home page.
Would you be willing to share some of your code, or at least the ideas
behind it so others could use it as well?
For anyone who’s interested, the code to do this is on the wiki,
Contributions->Extensions->HomePageSavedSearches
Steve