php redirect

blackhorse

For example, I have a long php scripts, reading dozens maybe hundreds rss feeds and parsing them, etc.

If in the middle of process, there is error such as feeds urls cannot be accessed, or rss fees formats are wrong, or it is not utf8 encoding as it should be etc. The process will be terminated. And error message will be displayed. And the end of this script will never be reached.

If in the middle of process, there are php notice shows (not error but notice), display the notice and continue the process.

If the process reaches the end, not terminated in the middle, then it means the process is successful (even in the middle of process, some php notice will be displayed), and then only at this point, I want to redirect to another page.

Usually, we can use the header redirect. But due to in the process, there are notices displayed, header redirect won't work.

I don't want to use javascript or meta tag client side redirect approach. Because this script could not only run from browser but also could run under command line on the server. So javascript or meta tag won't work always.

Any help?

bradgrafelman

Don't output the PHP errors - either log them or store them in a variable (e.g. by specifying your own error handler) and only output them if you need/want to.

blackhorse

bradgrafelman;10959368 wrote:
Don't output the PHP errors - either log them or store them in a variable (e.g. by specifying your own error handler) and only output them if you need/want to.

I used to log the php error and email a notice to myself if there is an error for production scripts.

But in this case, I want the errors to pop up, so the user of this script would be aware what is happening right away (such as which feed url fails etc.). This script is running under a folder under password protection. Any persons who have access to this folder (through web access or directly on the server) should be able to run the script and see the error if there is one.

The error message is not a problem here actually. Due to if there is an error, the process would be terminated and it wouldn't reach the end of the script - the success point, and page redirect is not needed.

My problem are there notices, I want to display these notices in the process but still let the process continue if there is notice. There are hundreds data feeds and there might be thousands cases if not less, could generate notices. But in average, maybe a dozen notices would be generated in each run. For the same reason I want the users to be aware of these notices when they run this script but no need to stop the process.

If the script reach the end of the point without error to terminate it, I want to sleep for 30 seconds, so the users would have a chance to read the notices. And then I want the script to redirect to another page.

Due to the notices are displayed, the php header location cannot be used. And due to it could be run on the server command line, client side redirect won't work either.

What can I do? Thanks!

bradgrafelman

I don't know that there is a solution to fit your requirements. You want to output client-side information as the script executes, yet at the end you don't want to use client-side coding to handle the redirect.

In other words, you can't have your cake and eat it too. :p

EDIT: Can you elaborate on the reasons why you don't want to use some client-side coding to redirect the person?

blackhorse

Does server side redirect have to use header redirect?

Such as could I use php to call some sh script and still do the redirect which would be both work either I run this script under command line or through the browser?

I am stuck here. Any advices?

Thanks!

blackhorse

Hello, bradgrafelman, thanks for your help.

Could I use output buffering? and then still use header to do the redirect if there are notices output before?

http://php.net/manual/en/function.ob-start.php

Thanks!

sneakyimp

You could write your own error handling function so that when an error is encountered, you can have your script do pretty much anything want. See [man]set_error_handler[/man].

An example might be to gather all the error handlers into a variable and feed that variable somewhere -- like into a database.

If you were to run a script as a background process using [man]exec[/man] then it might write progress to a file or database and you could have another script that displays in a browser which periodically refreshes itself and checks for errors being written.

Not really sure what you are after here though.

blackhorse

sneakyimp;10959451 wrote:
You could write your own error handling function so that when an error is encountered, you can have your script do pretty much anything want. See [man]set_error_handler[/man].

An example might be to gather all the error handlers into a variable and feed that variable somewhere -- like into a database.

If you were to run a script as a background process using [man]exec[/man] then it might write progress to a file or database and you could have another script that displays in a browser which periodically refreshes itself and checks for errors being written.

Not really sure what you are after here though.

Thanks! Actually that is the approach we are going to use.