--- "Beauford.2005" <[EMAIL PROTECTED]> wrote:
> It's obvious though that PHP can not handle it. This is why I am
> forced to use javascript. I have already spent a week on this
> and am not going to waste any further time.
So you sacrifice the experience of your users due to your own difficulties in
development? A developer's life is filled with problems; after all, your whole
job is to solve them. :-)
Stated differently, you should not be a problem solver if you don't like
problems.
> I have posted all my code and if someone can see a problem I'll
> look at it, but it just ain't worth the effort at this point.
I don't recall seeing your code, but it's possible that I ignored it because it
was "all your code" as you say. Huge, unintelligible chunks of code pasted into
email usually gets ignored by me (and possibly many other people). If you try
to make a small script that illustrates your misunderstanding or problem, you
will:
1. Probably figure out the problem yourself in the process of reproducing it
with a simple, focused script (10 lines or less should do).
2. Have some experienced people on the list quickly identify your error and
point you in the right direction if you still can't figure it out.
Remember that everyone on this list who helps out does so voluntarily. Help us
help you, else don't expect a lot of effort on our part. No one enjoys
hand-holding, and some people will (understandably so) get quite rude when they
feel that their efforts are being unfairly taken advantage of.
Now, I also remember showing you how to do a redirect in PHP already. There are
a few ways, but a protocol-based redirect (that uses a 300-level response
status code) can be performed like this:
header('Location: http://www.google.com/');
Does this not work for you? I'm sure it does.
Chris
=====
Become a better Web developer with the HTTP Developer's Handbook
http://httphandbook.org/
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
