redirect after processing

[[deleted]]

Hi all,
Does anyone know a way to automatically redirect my script after processing a form??? I do not want the user to be involved in redirecting.
The header()-function does not work in my script, problaby because I have used HTML tags, but even after removing these (+the blank lines) I still can't get header() to work. Anywayz, I was wondering whether or not there was another way (besides using header() ) to do this?!?!?!
TIA!! ;-)

[spacemax]

<?
if($redirect==true){
include($target);
}else{
?>
normalfile

[[deleted]]

I probably sound really blond, but could you explain your reaction??
To me, the include() function doesn't really seem to redirect me anywhere...
Does the 'normalfile' term have a specific meaning, cause I've never heard of it??!! %-(

[[deleted]]

I don't know why Dominik posted that either :-)

You could try using a javascript function, but that sucks.
Instead, try fixing your header problems. They do work if you have good clean code.

[lara8]

Clean code is a good thing, and I definitely agree that the header function does work. My main problem with the header-stuff is that I want to be able to compare user input with input allready stored in the database and warn the user in case of conflicts. Doing this generates code that must be processed before redirecting to whatever other file (where I would like to display the results of the users actions). The header-function doesn't like me doing this kind of stuff, and therefor... I don't like the header-function ;-) !!!

[[deleted]]

I suspect you only redirect if everything is ok, and when everything is ok, you don't print anything right?

[spacemax]

with the include function you can do something like this:

page1.php

---

something

---

page2.php

---

something else

---

page3.php

---

<?
if($redirect=='1'){
include('page1.php');
}else{
include('page2.php');
}
?>

---

if you call

page3.php?redirect=1

the output wil be

something

if page3.php?redirect=2

something else

this is, if you whant to see it like this a serverside redirect.

I use this code on many pages because the header doesent work fine, specialy in netscape..

[lara8]

What I want is to redirect after inserting the (approved) input, and displaying the inserted input in a new php-file. This, so that the user will not be able to reload his input using the browser (and therefor generating all kinds of annoying "allready exists"-errors).
Should it be the case that the input was << not >> approved, the user could also be redirected to a php-file describing the specific error that was made.

[lara8]

I don't think this would solve the problem why I initially have to redirect: the user must not be able to reload his input using the browser???!

[spacemax]

last try:

<?
$checkok='';
/IF INPUT TO PROCESS{ /
//Check input
/ } /
if($checkok=='OK'){
include('answer.php');
}
else{
include('form.php');
}
?>

if you call this file and there is no input to process $checkok will be empty, the formfile wil be shown.
if there is input, process it, if there is a problem, let $checkok be empty. the formfile will be shown.
if there is input and it is ok, set ächeckinput to OK and the answerfile will be shown.

is this the answer solving your problem?

[[deleted]]

In that case, what the 'f' is the problem? :-)

If there's an error you redirect, if there's no error you redirect. So the script that does the redirecting does not print anything (it would be lost because the redirect would move the browser to a different page before the user can see it)

[Anon]

Well i don't know if it helps, but when I redirect using javascript:

<script language="JavaScript" type="text/javascript">
<!--

self.location = 'newLocation.php3' ;

//-->
</script>

so if you put that after your code you should be okay? You may want to put in an :

if (!$error) {
...
} // end if no error

[lara8]

I'm almost afraid to say so ... but it's not a solution. By including files I would remain in my current file (say 2.php). When I reload using the browser, 2.php will try to process the input (entered in say 1.php) all-over-again. This was my original problem!!!
Then someone suggested I redirect (leave 2.php after processing without the user noticing it) to say 3.php. When a user then presses the reload button ... 3.php will not have the input from 1.php, and therefor I will not have the 'all-over-again' problem!
Thank you anyway for taking the time to help!

[lara8]

That's what I figured ... so why the 'h' doesn't it work??????????!!!!!!!!!!!!

[Anon]

Since you already have html tags... would Javascript be as suitable solution?

<script>
document.location = 'nextpage.php';
</script>

Just a suggestion...

[spacemax]

well, i see now...
small introduction to swissgerman:
Murks [read moorks in english]: solution which works but is not proper 😉

my murks to solve your problem:

<?
session_start();

$checkok='';
/IF INPUT TO PROCESS AND NOT SESS_PROCESSED==TRUE{ /
//Check input
//set SESSION_PROCESSED=TRUE
/ } /
if($checkok=='OK'){
include('answer.php');
}
else{
include('form.php');
}
?>

[Anon]

I hate to say this but redirection is not going to solve the reprocessing problem. It will just move the problem to the browsers back button. This is not a good solution since the back button is used much more often than the reload button.

To stop the reprocessing of information requires a check. This means you actually have to look to see if you've already processed the information once. If so then don't process it again.

<?
$check=0;
/Run your check on the information. If you've already processed it set $check=1 /
checkinfo();

if (!$check){
include(processinfo.php);
}

?>

This will mean that you will need some way of determining whether the information has been processed before or not.

[[deleted]]

Actually, one of the biggest problems of double-postings is that people are impatient and press reload after pressing submit, even before the reply page is complete.

that is the real problem.

There aren't many people who willingly use the back-button to go back and post the same thing again.

This solution is not 100% proof, but it catches about 90% of all double posts.

[[deleted]]

No, because javascript doesn't run untill the page is loaded, which is too late, and javascript is not reliable (people can switch it off)

[[deleted]]

Well what the "F" does the "F"ing code look like?

hey, this one-letter cursing is catchy :-)