[PHPLIB] ye`ol back button and forms From: Bob Strouper (bobw123 <email protected>)
Date: 12/28/99

hello,

There must be a suitable solution to users clicking
the back button after ( or during ) a form submission.

As we all know, many users will not stop using the back
button just if we ask them to , so where do we go from here?

Of course the ideal phplib cache seeting is "no" as we want
to keep state in such transactions as forms which
update/edit databases.

But, Netscape somtimes cannot even find the form, when hitting
the back button ( it errs with messages like "cannot find file
/path/to/NSform.tmp" ) and IE will always attempt to reload the
form.

So what is the solution? Do we use javascript to open up a
new window without the navigational bar? Do we make every
transaction an update? do we somehow tell the script that
it's a reload and do things accordingly ( but this would
still not fix the problem with netscape loosing the form file
alltogether )

I've also experimented with diabling phplibs cache
handling alltogether and then ( as someone on this list
suggested ) have all transactions UPDATES ..so if the user
hits the back button and then starts editing the same form
again, he is just screwing with the same record.

So, I wonder how the big boys do it? Honestly, I haven't
gone to many shopping sites ( I say shopping sites, not
because this is what I'm doing , but because I think, they
may be the best way to see how someone is using db tranactions
through a web/form interface ) , they must deal with this
problem in an elegent way.

I look forward to all your comments, and what methods you have
come to use. I'm thinking, opening up a new window apon
authentication, and creating my own navigation might be the
only way to truly contole things.

Bob

______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com?sr=mc.mk.mcm.tag001

-
PHP3 Base Library Mailing List. Send messages to <phplib <email protected>>.
To unsubscribe, send "unsubscribe" to <phplib-request <email protected>> in
the body, not the subject, of your message.