Dear PHPPP,

I have read in changelog from 2.0.18 to 2.0.18.1 that you have made this change:

Improved: Turned enableRegenerateId off in XOOPS session to avoid problems with IEs (phppp)

But using private sessions with this setting, it seems impossible to login (explorer 6 and firefox 2.0.0.12 in a system updated from 2.0.9 to 2.0.18.1)

I find no setcookie anywhere for private session, other than in session.php (update_cookie) and it seems to be called only with enableRegenerateId true.

I need to set enableRegenerateId On in the script (kernel/session.php) to make it work.

I couldn't yet test it with explorer 7.

Could it give some problems?

Thank you, bye. Have a good work (could you say like this? bleah ... my terrible english )

Sorry, I just read now the change log 2.0.18.1:

Improved: Turned enableRegenerateId off in XOOPS session to avoid problems with IEs (phppp)

It avoid some problems but it seems it generates other problems ... i think best thing now is don't use personal session.

Ciao

Hi guys,

for me is a problem introduced with 2.0.18.1:

file kernel/session.php line 78:

2.0.18
var $enableRegenerateId = true;

2.0.18.1
var $enableRegenerateId = false;


I had problems with login with personal sessions.
I have put true the var $enableRegenerateId in the kernel/session.php and everything seems to work fine.

I don't know if they set it to false for something else.

Is it so or is it a simple forgot?

If you don't need personal session also setting my_session to 0 in the xoops_config table in the use_mysession field can work.

Hope it help.

ciao