|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #42472 $_SESSION[false] = 1; Notice: Unknown: Skipping numeric key 0. in Unknown on
Submitted: 2007-08-29 17:05 UTC Modified: 2007-08-30 09:16 UTC
Avg. Score:3.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:0 (0.0%)
From: jsnell at e-normous dot com Assigned:
Status: Not a bug Package: Session related
PHP Version: 5.2.3 OS: 10.4.10
Private report: No CVE-ID: None
 [2007-08-29 17:05 UTC] jsnell at e-normous dot com
Attempting to use an array key of false on $_SESSION after a session has 
been started causes a notice without sufficient information to fix the 

Also tested in latest CVS: PHP 5.2.4RC4-dev (cgi) (built: Aug 29 2007 

Reproduce code:
$_SESSION[false] = 1;

Expected result:
Notice: Unknown: Skipping numeric key 0. in test.php on line 3

Actual result:
Notice: Unknown: Skipping numeric key 0. in Unknown on line 0


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2007-08-29 20:23 UTC]
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at and the instructions on how to report
a bug at

false/true/null/etc are not valid key names. Please read the manual for what is valid and what isn't. This is no bug.
 [2007-08-29 20:57 UTC]
This isn't exactly the problem. The problem is that the error 
message produced is incorrect -- not that the error shouldn't occur. 
It should not have an unknown file and a 0 line number, but rather 
the file and line number where the error occurred.

This is probably superglobal-array-specific, and seems to apply to 
any numeric key.

 [2007-08-30 09:16 UTC]
Rebogused: This is not possible to change and that's how it works.

 [2011-05-17 19:39 UTC] fgutierrez at ticomotorsports dot com
This is clearly a bug in PHP.

The answer from leaves too much to desire. Seems like jani was "washing their hands" and leaving the problem to anyone else.
 [2012-11-03 13:45 UTC] aminviral2006 at gmail dot com
I just encountered with this problem.
my session was like $_SESSION[0]['someid']

and i changed it to $_SESSION['someid'][0]
now it works fine.

Hope this helps you
 [2013-07-30 02:05 UTC] aerosox at gmail dot com
Just to elaborate a little bit on why this didn't work for future readers. 
register_globals. PHP 5.4 has removed support for register_globals, so going 
forward you can in fact use numeric keys with $_SESSION. 

$_SESSION is a super global variable and they were treated "special" with 
register_globals. One of the things that makes a super global special is that it 
exists in all scopes without needing to use the 'global' keyword. With 
register_globals the other thing that made it special is that it creates 
variables for all of the child elements automatically... again in all scopes.

$_SESSION['username'] = 'Test';

The above would also set a variable $username = 'Test'; So if there was a 
= 'Test'; It would attempt to set $1 = 'Test' which is not allowed. So when jani 
said it was not possible to change, what was meant was it was not possible to 
change without 6 years of planning to remove register_globals support.
 [2017-10-10 20:52 UTC] jhawkins at locutius dot com
Replies to this continue to miss the point... The bug is not that the functionality around $SESSION is a wrong. It is that the error message is unhelpful when a person trips over this.

NOTE: The issue also happens when using this:
  $_SESSION[] = 1;

Or this:
   $row = <function that returns array from PDO::FETCH_BOTH or PDO::FETCH_NUMERIC>;
    if (!empty($row)) {
      foreach ($row as $key => $val) {
        $_SESSION[$key] = $val;

Shouldn't the message be something like:
  NOTICE: Unknown: Skipping unsupported numeric key assignment in $SESSION array.

And if possible (though I gather it's not), seems it should indicate the offending line of code.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Jun 18 18:01:32 2024 UTC