On 21/07/15 08:48, Tom Robinson wrote: > 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:
'<a href="/rt3/Ticket/Display.html?id=__id__">__id__</a>/TITLE:#', '<a href="/rt3/Ticket/Display.html?id=__id__">__Subject__</a>/TITLE:Subject', Probably should look more like these: '<b><a href="__WebPath__/Ticket/Display.html?id=__id__">__id__</a></b>/TITLE:#', '<b><a href="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></b>/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
Description: OpenPGP digital signature
