[#19127] - PHP Warning: session_set_save_handler() & session_set_cookie_params()
- Closed
- 28 Dec 2017
- Medium
- Build: staging
- # 19127
Steps to reproduce the issue
Just upgraded to PHP 7.2.0
Go to the front end.
Log in.
See php error log.
Actual result
PHP Warning: session_set_save_handler(): Cannot change save handler when session is active in \libraries\joomla\session\storage.php on line 106
PHP Warning: session_set_cookie_params(): Cannot change session cookie parameters when session is active in \libraries\src\Session\Session.php on line 807
System information (as much as possible)
PHP 7.2.0
| Labels |
Added:
?
|
||
franz-wohlkoenig
- | Category | ⇒ | Front End |
| Status | New | ⇒ | Confirmed |
| Status | Confirmed | ⇒ | Information Required |
Sadly no.
Just want to add that this issue happens when user logs in and seems like a bug in fork method of Session class https://github.com/joomla/joomla-cms/blob/staging/libraries/src/Session/Session.php#L792
I don't understand deep enough about session, however, look like https://github.com/joomla/joomla-cms/blob/staging/libraries/src/Session/Session.php#L804 doesn't need to be called as the session is active (comment it will solve the first warning)
Also, I am not sure this command https://github.com/joomla/joomla-cms/blob/staging/libraries/src/Session/Session.php#L811 is needed as because after the previous line called $this->_handler->regenerate(true, null);, session is started already
@mbabker Could you please take a look at this issue?
| Status | Information Required | ⇒ | Discussion |
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-12-28 15:34:56 |
| Closed_By | ⇒ | franz-wohlkoenig |
| Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/19127
Have same issue, solved copy this into php.ini
error_log=C:\Windows\temp\PHP7_errors.log
upload_tmp_dir=C:\Windows\temp
session.save_path=C:\Windows\temp
cgi.force_redirect=0
cgi.fix_pathinfo=1
fastcgi.impersonate=1
fastcgi.logging=0
max_execution_time=300
date.timezone=Europe/Belgrade
I can confirm the issue. Updated our website to PHP 7.2 last week and saw the same warning in error logs