Quote:

I never said you could?

Did it make any hacks to the core of XOOPS files?

Did it make any DB changes?

Quote:

From that I would say not, unless you revert those changes, I would say upgrade is impossible, unless you know what to do, or some one that knows what to do, does it for you.

You've turned sessions off now, so it won't display a session ID, you now use Cookies which stores information on the users computer, rather than the DB.

You can change the user cookie to one of your own though!

If you wish to know the difference or how they work, you could do a search on google or something cookies Vs Sessions. Or a dev maybe kind enough to explain for you.

great! thank you so much !

i ll go to the newbbpro thread to see what they are saying, maybe i m not the only one who have this problem !

and for persons who had the same problem as i, (about phpsessid) it will be safer for you to use cookies
(well it was the case for me)

Xoops rocks!

Not a problem at all, hope I've helped in some way.

Take care

I got started down this path for a different reason. I would know enough to not send someone a PHPSESSIONID string.

I'm trying to validate my page with the W3C XHTML 1.0 validator. And it barfs on the unescaped ampersand before the PHPSESSIONID string. Can this be fixed, and if so how ?


Secondly, why does the use of custom sessions require putting the session id in the URL strings ? Why couldn't they be put in cookies like any other session ?