* James [EMAIL PROTECTED]:
Actually:
Will there be an issue with the back button if I use 1 script to do
all of what I posted before?
No.
Thank you guys for the answers. I think I will go with the following
approach.
(A) script 1 submits to script 2 then
(B) script 2 redirects
Thank you guys for the answers. I think I will go with the following approach.
(A) script 1 submits to script 2 then
(B) script 2 redirects browser back to script 1
Script 1 is in charge of submitting and displaying; script 2 does the
processing.
This list is the best!
-James
At 2:08 AM +
Actually:
Will there be an issue with the back button if I use 1 script to do
all of what I posted before?
So...
Script 1 submits to itself...it does the processing, updates
databases, etc...then it redirects back to itself for displaying for
results.
-James
Thank you guys for the answers.
Currently I have an application with PHP scripts that passes POST
variables to keep track of ID's of records, the processing mode and
such.
I totally didn't design it to handle when a user hits the Back button
in the browser...everything is tightly controlled...The user clicks
on
On 4/26/05, James [EMAIL PROTECTED] wrote:
What have people done in the past to deal with states and such and
keeping these things straight when the user hits the BACK button?
Use GET instead of POST for your form method. And if you need both
methods just handle the incoming requests from the
I apologize in advance if I'm asking basic questions...
When you hit the back button, won't the browser just take the page
from the cache?
I haven't switched my POSTs to GETs and this is what I'm seeing.
I have a list of images. There are check boxes next to the images.
When the user checks
Ok Greg:
I changed everything to GET and it's behaving better! Thanks.
I guess when the user clicks the back button they should just get
back the last state of the browser...no if, and or but's.
-James
At 1:59 PM -0500 4/26/05, Greg Donald wrote:
On 4/26/05, James [EMAIL PROTECTED] wrote:
What
I changed everything to GET and it's behaving better! Thanks.
I guess when the user clicks the back button they should just get
back the last state of the browser...no if, and or but's.
This is because when you click the back button on the browser it pulls
up the URL from it's history
* James [EMAIL PROTECTED]:
I apologize in advance if I'm asking basic questions...
When you hit the back button, won't the browser just take the page
from the cache?
I haven't switched my POSTs to GETs and this is what I'm seeing.
I have a list of images. There are check boxes next to the
On Tue, April 26, 2005 11:51 am, James said:
What have people done in the past to deal with states and such and
keeping these things straight when the user hits the BACK button?
Best Option:
Don't design your application like that :-)
People use the browsers they use because they like its
10 matches
Mail list logo
