Upgraded PHP, annoying errors...

[Mong]

I upgraded to the latest PHP (having not upgraded in about 10 months previously!).

Now I get lots of stuff like:

Notice: Undefined variable: existingerror in H:\Dev\sc\login.php on line 104

or

Notice: Undefined index: m in H:\Dev\sc\index.php on line 3

Now, I know this is caused because I use (respectively):

if ((!$existingerror) and (!$row['active']))
if ($_GET['m'] == "logout")

So (as far as I can see) I have two choices:

1 - Add "^E_NOTICE" to the PHP config
or
2 - Do if (isset ($_GET['m']) and ($_GET['m']=="logout"))

The problem with (1) is that I'll no longer know if I've mispelled a variable elsewhere. But with (2) I'll have to rewrite a LOT of code. Not just for this project, but for lots of others.

Can anybody suggest a 3rd Way? I suppose I _could_ turn off display_errors and refer to the error log if something doesn't work. But that sucks. I want my errors on screenm there and then! Well, errors apart from ones moaning about undefined variables.

It's amusing, because one of the good things(?) about PHP, is that you never needed to define or cast variables prior to use.

Grrr...

M.

[Mit]

You can turn off error messages on a per page basis... turn them on for development and off on the live server?

don't just have hte command here, will have a look when i get home

[Mong]

Yes mate, but that does mess us up, doesn't it?

It would mean I no longer get an error for if (!$foo), sure. But if for example I do:

$foo = 1
$bar = 2
$total = $foo+$bra


Then with this (above) I won't get informed that $bra doesn't exist.

Bah!

M.

[Mit]

Hence why i said about having it OFF for development and ON for live

[JetLinus]

Not declaring your variables is BAAAAAAAD man!
Pure evil!

[queball]

Always put m= in your URLs?

[Mong]

Originally Posted by JetLinus

Not declaring your variables is BAAAAAAAD man!
Pure evil!

Erm, PHP has never required you to declare your variables.

So usually, I'd agree. But with regards to PHP, you're not right I'm afraid.

M.

[Mong]

Originally Posted by Mit

Hence why i said about having it OFF for development and ON for live

That's stupid Mr Mit.

What if I DID spell a variable name wrong?

I'd never know.

M.

[JetLinus]

Ah ok, sorry then :-/

But did I understand correctly? If you had declared your variables, this could not have happened?

Or anyway, doesn't PHP force you to declare your vars, or doesn't it allow you to?


Because if you are able to, you should. Actually... You know, oldschool-style.
That's what my point was.

[Mit]

Originally Posted by Mong

That's stupid Mr Mit.

What if I DID spell a variable name wrong?

I'd never know.

M.

You'd know cos you would have the thing turned off while developing and then turn it on when you upload to the live server....

don't tell me, you edit the live copy?

[Mong]

Originally Posted by Mit

You'd know cos you would have the thing turned off while developing and then turn it on when you upload to the live server.... =

Yes. What's the point of developing without seeing error messages? Your suggestion means I wouldn't know of errors in my code until I uploaded it!!

Originally Posted by Mit

don't tell me, you edit the live copy?

Of course not.

M.

[MT]

The reason is that you have error reporting set to E_ALL, whereas normally it is E_ALL & !E_NOTICE


JetLinus: I think the day that there is a php -w I will jump for joy.

[Mit]

Originally Posted by Mong

Yes. What's the point of developing without seeing error messages? Your suggestion means I wouldn't know of errors in my code until I uploaded it!!

crossed meanings, i mean turn OFF the "hide errors" thing while developing and then on when u upload, thus u CAN see the errors on Dev and not on Live