Posted by Bent Stigsen on 06/10/06 15:42

Craig Morrison wrote:
[snip]
> Why don't you just say that you don't know?
>
> Or is it that you just feel a need to be verbose for no reason?
>
> Here is the entire mess of code.. You tell me why the notice is thrown
> if you can, otherwise shut the fuck up.

Oh, sticks and stones Craig, I am too old to care about your huffing and
puffing. And you are free to ignore anything I say.

The notice get thrown because there is an undefined index, just as the
notice says, but I can't tell you the exact circumstances. For that, I
would have to look over your shoulder, and see exactly how the things are
used and what comes out of it, and not just the things you find relevant to
tell. If it was visible from that, you would probably have seen it.

What I do know (or atleast put my reputation on the line for), is that if
the form posts the D1 value, as you say it does, then there is *no way*
that $_POST['D1'] is generating a notice. Period.
That is why I said you should treat it as a bug/flaw somewhere in your
construction, because effectively it would mean that you had an unhandled
state. But from your code you posted, I can see that you verify the value
afterwards, so it is not critical.

What Geoff suggest (using isset before accessing the value) lets you decide
what to do in cases where the value is not set. That will remove the
clutter from your log-files.

[snip code]
Ok, seen it.

> I have left *nothing* out, so now, if you or anyone else can please tell
> me why the notice is thrown.

Just a few things.
What is the exact full message (notice) you get.
How is the index.php page initially accessed. (get/post, args)

/Bent

[Back to original message]