Check if $_GET["menu"] is null.

[Nuno Paquete]

Hi group.
I'm using this code to see if is there any parameter for variable "menu":

if($_GET["menu"] == "downloads" )
....

But this code log errors if there is no parameter passed (this heappens at
the first time the page is loaded).

I tryed this code:

if($_GET["menu"] != ""){
if($_GET["menu"] == "downloads" )
...

But this log the same error on the second line.
Any help hould be greattly appreciated.
Thanks in advance,

Nuno Paquete

[Gary L. Burnore]

On Fri, 30 Jul 2004 18:22:43 +0100, Nuno Paquete <nm*@ispgaya.pt >
wrote:

Hi group.
I'm using this code to see if is there any parameter for variable "menu":

if($_GET["menu"] == "downloads" )
....

But this code log errors if there is no parameter passed (this heappens at
the first time the page is loaded).

I tryed this code:

if($_GET["menu"] != ""){
if($_GET["menu"] == "downloads" )
...

Look at the isset() function.
--
gburnore@databa six dot com
---------------------------------------------------------------------------
How you look depends on where you go.
---------------------------------------------------------------------------
Gary L. Burnore | ÝÛ³ºÝ³Þ³ºÝ³³ÝÛº ݳ޳ºÝ³Ý³Þ³ºÝ³Ý ÝÛ³
| ÝÛ³ºÝ³Þ³ºÝ³³ÝÛº ݳ޳ºÝ³Ý³Þ³ºÝ³Ý ÝÛ³
DataBasix | ÝÛ³ºÝ³Þ³ºÝ³³ÝÛº ݳ޳ºÝ³Ý³Þ³ºÝ³Ý ÝÛ³
| ÝÛ³ 3 4 1 4 2 ݳ޳ 6 9 0 6 9 ÝÛ³
Black Helicopter Repair Svcs Division | Official Proof of Purchase
=============== =============== =============== =============== ===============
Want one? GET one! http://signup.databasix.com
=============== =============== =============== =============== ===============

[Jeffrey Silverman]

On Fri, 30 Jul 2004 18:22:43 +0100, Nuno Paquete wrote:

But this code log errors if there is no parameter passed (this heappens at
the first time the page is loaded).

What errors? I don't see why you would get any. PHP is fairly quiet
about using variables that are not yet set.

--
Jeffrey Silverman
je**********@jh u.edu
** Drop "PANTS" to reply by email

[steve]

"Gary L. Burnore" wrote:

On Fri, 30 Jul 2004 18:22:43 +0100, Nuno Paquete
<nm*@ispgaya.pt >
wrote:

Hi group.
I’m using this code to see if is there any parameter for

variable "menu":

if($_GET["menu"] == "downloads" )
....

But this code log errors if there is no parameter passed (this

heappens at

the first time the page is loaded).

I tryed this code:

if($_GET["menu"] != ""){
if($_GET["menu"] == "downloads" )
...

Look at the isset() function.

Try isset first followed by $_GET... as in
if (isset(....) && $_GET[....] ) do something;

php would not look at the $_GET in the above condition unless the
left-side conditional isset(..) is True. By the way, even if you
don’t use isset, you should get a warning, and not an error.

--
http://www.dbForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbForumz.com/PHP-Check-_G...ict135082.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbForumz.com/eform.php?p=451195

[Garp]

"steve" <Us************ @dbForumz.com> wrote in message
news:41******** **@news.athenan ews.com...

"Gary L. Burnore" wrote:

> On Fri, 30 Jul 2004 18:22:43 +0100, Nuno Paquete
> <nm*@ispgaya.pt >
> wrote:
>

> >Hi group.
> >I'm using this code to see if is there any parameter for

> variable "menu":

> >
> > if($_GET["menu"] == "downloads" )
> > ....
> >
> >But this code log errors if there is no parameter passed (this

> heappens at

> >the first time the page is loaded).
> >
> >I tryed this code:
> >
> > if($_GET["menu"] != ""){
> > if($_GET["menu"] == "downloads" )
> > ...

>
> Look at the isset() function.
>
>

Try isset first followed by $_GET... as in
if (isset(....) && $_GET[....] ) do something;

php would not look at the $_GET in the above condition unless the
left-side conditional isset(..) is True. By the way, even if you
don't use isset, you should get a warning, and not an error.

I'm partial to array_key_exist s($needle, $haystack) myself.

Garp

[Tino Didriksen]

Like this:

if (!empty($_GET['menu'])) {
if ($_GET['menu'] == 'downloads') {
...
} else if ...
}

-- Tino Didriksen / Project JJ

[Andy Hassall]

On Fri, 30 Jul 2004 21:07:49 GMT, "Garp" <i_**@home.no w> wrote:

I'm using this code to see if is there any parameter for
variable "menu":

if($_GET["menu"] == "downloads" )
....

But this code log errors if there is no parameter passed (this
heappens at the first time the page is loaded).

Look at the isset() function.

Try isset first followed by $_GET... as in
if (isset(....) && $_GET[....] ) do something;

php would not look at the $_GET in the above condition unless the
left-side conditional isset(..) is True. By the way, even if you
don't use isset, you should get a warning, and not an error.

I'm partial to array_key_exist s($needle, $haystack) myself.

Whilst it seems a bit "naughty" from a purist point of view, I tend to use
@$_GET['x'] - i.e. use error suppression, rather than "isset then use array
key". So:

if (@$_GET['x'] == "something" )
// do something;
else
// either don't do something, or whinge that it's not an expected value

I can't off the top of my head think of any other possible error that it could
mask, other than the notice of use of undefined variable. In this case,
undefined leads to the condition being false, so it doesn't get any further
than that.

--
Andy Hassall <an**@andyh.co. uk> / Space: disk usage analysis tool
http://www.andyh.co.uk / http://www.andyhsoftware.co.uk/space

[Zurab Davitiani]

Andy Hassall wrote:

Whilst it seems a bit "naughty" from a purist point of view, I tend to
use
@$_GET['x'] - i.e. use error suppression, rather than "isset then use
array key". So:

if (@$_GET['x'] == "something" )
// do something;
else
// either don't do something, or whinge that it's not an expected value

I can't off the top of my head think of any other possible error that it
could
mask, other than the notice of use of undefined variable. In this case,
undefined leads to the condition being false, so it doesn't get any
further than that.

If you try these
if(@$_GET['x'] == 0)
if(@$_GET['x'] == false)
then they will evaluate to true, even though x key is undefined. You can try
with === but then you lose the flexibility of type conversion.

[Andy Hassall]

On Fri, 30 Jul 2004 22:10:51 GMT, Zurab Davitiani <ag*@mindless.c om> wrote:

Andy Hassall wrote:

Whilst it seems a bit "naughty" from a purist point of view, I tend to
use
@$_GET['x'] - i.e. use error suppression, rather than "isset then use
array key". So:

if (@$_GET['x'] == "something" )
// do something;
else
// either don't do something, or whinge that it's not an expected value

I can't off the top of my head think of any other possible error that it
could
mask, other than the notice of use of undefined variable. In this case,
undefined leads to the condition being false, so it doesn't get any
further than that.

If you try these
if(@$_GET['x'] == 0)
if(@$_GET['x'] == false)
then they will evaluate to true, even though x key is undefined.

Yes, fair point, this falls over when expecting values that implicitly convert
to false. It's OK for doing switches e.g. on an 'action' value if you're only
expecting non-false values such as 'add', 'edit', etc., but it's dangerous
laziness if numeric values are coming in. Ah well, I knew it was bad really :-)

--
Andy Hassall <an**@andyh.co. uk> / Space: disk usage analysis tool
http://www.andyh.co.uk / http://www.andyhsoftware.co.uk/space

[Nuno Paquete]

Andy Hassall wrote:

On Fri, 30 Jul 2004 21:07:49 GMT, "Garp" <i_**@home.no w> wrote:

>I'm using this code to see if is there any parameter for
> variable "menu":
>
> if($_GET["menu"] == "downloads" )
> ....
>
>But this code log errors if there is no parameter passed (this
>heappens at the first time the page is loaded).

Look at the isset() function.

Try isset first followed by $_GET... as in
if (isset(....) && $_GET[....] ) do something;

php would not look at the $_GET in the above condition unless the
left-side conditional isset(..) is True. By the way, even if you
don't use isset, you should get a warning, and not an error.

I'm partial to array_key_exist s($needle, $haystack) myself.

Whilst it seems a bit "naughty" from a purist point of view, I tend to
use
@$_GET['x'] - i.e. use error suppression, rather than "isset then use
array key". So:

if (@$_GET['x'] == "something" )
// do something;
else
// either don't do something, or whinge that it's not an expected value

I can't off the top of my head think of any other possible error that it
could
mask, other than the notice of use of undefined variable. In this case,
undefined leads to the condition being false, so it doesn't get any
further than that.

--
Andy Hassall <an**@andyh.co. uk> / Space: disk usage analysis tool
http://www.andyh.co.uk / http://www.andyhsoftware.co.uk/space

Thank you guys. It's working without errors.
I used "@$_GET ..." but isset() function works perfectly.

Jeffrey, the error that I was getting is:

[Fri Jul 30 20:48:28 2004] [error] PHP Notice: Undefined index: menu in
home/nuno/public_html/header.php on line 124

Best regards,

Nuno Paquete