Saved search results have wrong URL

RT Users
1

Hi,

I’ve just updated from RT 4.0.2 to RT 4.2.11 but have an issue with my saved search results
generating links with /rt3/ in the path. When I remove the /rt3/ component from the URL manually, I
can browse to the ticket.

Here’s what the search generates for a ticket link:

http://myrt4/rt3/Ticket/Display.html?id=2379

But when I click through I get ‘Page not found - The page you requested could not be found - Please
check the URL and try again.’

If I manually remove the /rt3/ component in the location bar, I can browse to the ticket:

http://myrt4/Ticket/Display.html?id=2379

What is happening to corrupt the ticket URLs?

Kind regards,
Tom

Tom Robinson
IT Manager/System Administrator

MoTeC Pty Ltd

121 Merrindale Drive
Croydon South
3136 Victoria
Australia

T: +61 3 9761 5050
F: +61 3 9761 5051
E: tom.robinson@motec.com.au

signature.asc (181 Bytes)

2

Hi,

I’ve just updated from RT 4.0.2 to RT 4.2.11 but have an issue with my saved search results
generating links with /rt3/ in the path. When I remove the /rt3/ component from the URL manually, I
can browse to the ticket.

Here’s what the search generates for a ticket link:

http://myrt4/rt3/Ticket/Display.html?id=2379

But when I click through I get ‘Page not found - The page you requested could not be found - Please
check the URL and try again.’

If I manually remove the /rt3/ component in the location bar, I can browse to the ticket:

http://myrt4/Ticket/Display.html?id=2379

What is happening to corrupt the ticket URLs?

Found it. The query has corrupted/bad hrefs:

‘id/TITLE:#’,
‘Subject/TITLE:Subject’,

Probably should look more like these:
‘id/TITLE:#’,
‘Subject/TITLE:Subject’,

I’ve since found a couple of saved queries that exhibit the same behaviour. All queries have a
specific CustomField in the search criteria. I’ve not found the exact cause of the conflict but it’s
not so onerous to recreate these queries.

signature.asc (181 Bytes)