wrong subject

Same problem with this Code example:

<?php
ob_Start();
session_start();

var_dump($_SESSION);

$_SESSION['asdf'] = "cool";

$tmp = $_SESSION;

$cool = 'test';

$_SESSION['me'] = $cool;

var_dump($_SESSION);

Here is also an interesting issue:

When i use the 2nd example code ( the one with $tmp = $_SESSION);

and i put

unset($tmp);

after it or try to assign 
$tmp['x'] = 'y';

then the $_SESSION assignment startin again to work. Please investigatte ASAP.

Can i get a status update on this bug?

>Can i get a status update on this bug?
Yes. Don't try to outsmart session extension by changing $_SESSION array itself. This way $_SESSION looses its magical features and the only result you can get is invalid/broken data.
This is expected and I have serious doubts it's going to be changed ever.

Ok, but still, there is nothing in the documentation that explain this problem or show it, how to avoid it.

Moved to Documentation problem

So, does this get fixed at least in the documentation? :)

I still don't understand why this can't get fixed, a lot of user crys because of the 'magic feature' of the session and such problems.

Any status update on this bug??? Not hard to add in documentation

-.-

Updated information that this is general

We welcome a patch from you.
I however don't see the need to document it, will only add 
confusion.

I do not agree that this is a documentation problem, or that describing it as ?expected behaviour? is a suitable response. If PHP is a robust language, it cannot have unexpected and obscure rules applied at random. $_SESSION should just be an array that persists between page requests, providing session_start() has been called: that is what everyone expects and that is how it is used.

In every other case, $new_array = $existing_array; is a value assignment and simply copies one array to another and no alteration is made or should be expected to $existing_array or its properties.

I have spent several days trying to work out why my sessions weren?t working as I expected and taken up the time of several helpful posters in various fora. I finally tracked the problem down to this issue and some code included in every page of a widely used forum; an otherwise robust and secure open source product. I seriously doubt that a note in the documentation would have saved me much of this work and none of the work needed to get around the issue, once it was identified. This will apply equally to all those who fall foul of this problem ? you need to know what the problem is before searches will turn up documentation.

Mike

As described above, adding a note is not appropriate as it will more than likely add confusion. 

Changed back to session related issue. Not fixed or commented yet

.