I guess you could disable the submit button on first submit? ... on
server side you could get rid of the processing function from the
cache that is associated with that specific thing. However this kind
of seems unnecessary for your use-case ... maybe.
Br's,
Marius
On Oct 3, 3:55 am, Oliver
I guess you could disable the submit button on first submit? ... on
server side you could get rid of the processing function from the
cache that is associated with that specific thing. However this kind
of seems unnecessary for your use-case ... maybe.
Its funny you mention that Marius - not
On Oct 3, 2:11 pm, Tim Perrett [EMAIL PROTECTED] wrote:
I guess you could disable the submit button on first submit? ... on
server side you could get rid of the processing function from the
cache that is associated with that specific thing. However this kind
of seems unnecessary for
On Thu, Oct 2, 2008 at 5:55 PM, Oliver [EMAIL PROTECTED] wrote:
Thanks for the answers
Another related question - Is there any functionality in lift to prevent
multiple submits (e.g. the browser is slow for whatever reason and the user
presses the submit button multiple times)?
I'll add
On Thu, Oct 2, 2008 at 5:13 PM, Oliver [EMAIL PROTECTED] wrote:
I'm writing a wizard-like process, where when they have finished the set of
forms and press submit I don't want the back button to take them back. Is
there any way I can clear out the history?
This is JavaScript magic and I'm
Thanks for the answers
Another related question - Is there any functionality in lift to prevent
multiple submits (e.g. the browser is slow for whatever reason and the user
presses the submit button multiple times)?
cheers
Oliver
On Fri, Oct 3, 2008 at 10:15 AM, David Pollak [EMAIL PROTECTED]
