"Ticket couldn't be loaded"

RT-1-3-94

The transaction notice on ticket creation has a URL to the ticket. Clicking
on this URL will give you an RT login prompt. Logging in will give you
"Ticket couldn’t be loaded". However, you can get to it easily using the
"Goto ticket ___" button.

The Apache log records this each time as: “WebRT: Ticket couldn’t be loaded
()”. This is also true for the RT logs (same exact log entry).

Other than this RT seems flawless. Anyone know the answer to this annoying
problem?

TIA,

Carl Potter

I’ve not seen this before. But i’ve got a few ideas.

    If you click on the link again after you log in, does it work?
    What is the exact form of the link? (Can you provide an example?)On Wed, Jun 20, 2001 at 12:53:30PM -0700, Carl Potter wrote:

RT-1-3-94

The transaction notice on ticket creation has a URL to the ticket. Clicking
on this URL will give you an RT login prompt. Logging in will give you
"Ticket couldn’t be loaded". However, you can get to it easily using the
"Goto ticket ___" button.

The Apache log records this each time as: “WebRT: Ticket couldn’t be loaded
()”. This is also true for the RT logs (same exact log entry).

Other than this RT seems flawless. Anyone know the answer to this annoying
problem?

TIA,

Carl Potter


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

…realized that the entire structure of the net could be changed to be made
more efficient, elegant, and spontaneously make more money for everyone
involved. It’s a marvelously simple diagram, but this form doesn’t have a way
for me to draw it. It’ll wait. -Adam Hirsch

If you do a “Goto ticket ___” first, then go somewhere else within RT, and
then hit the original URL again it works.

It even works after you’ve logged out. It seems constant that it will work
if you do a “Goto ticket ___”, but not if you browse to it.

Hitting the link from the email transaction a 2nd time will just continue to
prompt you to log in.

Here is the form of the link that is given in the email:
http://./Ticket/Display.html?id=<#>

The line in my Transaction Scrip that makes the URL looks like this: Ticket
<URL: {$RT::WebURL}Ticket/Display.html?id={$Ticket->id} >

This is identical to the URL you’d get after you do a “Goto ticket ___” or
browse down to the ticket.

There is one other person in the list that has reported this (found it when
I was trying to fix it myself).

Thanks,

Carl PotterFrom: Jesse [mailto:jesse@fsck.com]
Sent: Wednesday, June 20, 2001 3:00 PM
To: Carl Potter
Cc: rt-devel@lists.fsck.com; Brian Paquette
Subject: Re: [rt-devel] “Ticket couldn’t be loaded”

I’ve not seen this before. But i’ve got a few ideas.

    If you click on the link again after you log in, does it work?
    What is the exact form of the link? (Can you provide an example?)

RT-1-3-94

The transaction notice on ticket creation has a URL to the ticket.
Clicking
on this URL will give you an RT login prompt. Logging in will give you
"Ticket couldn’t be loaded". However, you can get to it easily using the
"Goto ticket ___" button.

The Apache log records this each time as: “WebRT: Ticket couldn’t be
loaded
()”. This is also true for the RT logs (same exact log entry).

Other than this RT seems flawless. Anyone know the answer to this
annoying
problem?

TIA,

Carl Potter


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

…realized that the entire structure of the net could be changed to be made

more efficient, elegant, and spontaneously make more money for everyone
involved. It’s a marvelously simple diagram, but this form doesn’t have a
way
for me to draw it. It’ll wait. -Adam Hirsch