I played a little with web/api.py, Request.display() method.
Around line 150 it has:
self.send_header('Cache-control', 'must-revalidate')
self.send_header('Expires', 'Fri, 01 Jan 1999 00:00:00 GMT')
So I replaced the 2 lines above (commented those out) with just this one:
self.send_header('Expires', 'Thu, 01 Jan 2099 00:00:00 GMT')
That seem to have done the trick. Not sure what long-term implications that
will have though. Will continue playing with the system...
Vladimir
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt Good
Sent: Wednesday, August 16, 2006 10:38 AM
To: [email protected]
Subject: Re: [Trac] How not lose ticket data on TracError?
On Mon, 2006-08-14 at 19:59 -0700, Vladimir Sushkov wrote:
> Hello,
>
> Is there any way/hack/patch to keep previously filled ticket data if
> a TracError is raised during a new ticket creation or existing ticket
> update?
> For example, a user created a ticket but forgot to fill in the Summary.
> When they submit the ticket Trac gives the error page:
> Error
> Tickets must contain a summary.
> When the user clicks Back button on his/her browser, they are faced with
an
> empty ticket form. All previously filled data gets lost, and it may be a
lot
> of text if the issue is big, so they user is forced to repeat all the
input
> over again...
Well, browsers like Firefox retain the form inputs, so if you get an
error you can hit "Back" and your data will still be there. But I am
not aware of a patch to handle this on the server-side.
--
Matt Good <[EMAIL PROTECTED]>
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
