You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying out Grav on my Linux laptop. Ubuntu 18.04 LTS, php (7.2), nginx, php-fpm from system packages. Nginx config from webserver-configs directory with a modified server_name directive to match the website hostname configured in /etc/hosts.
When accessing http://mysitename.local/ for the first time, I get an exception with a stack trace.
The root cause is that $options arrays has keys with session. prefixes when invoking session_start() in system/src/Grav/Framework/Session/Session.php line 192. That is incorrect. The docs for session_start() explicitly say that $options array should not have session. prefixes.
Here is the array I get
I would have provided a patch but I am not yet familiar with the codebase. The patch I hacked works for me, but I need to learn how to run the test suite if Grav has one...
The error should have been caught by others but for some reason I am the person reporting it... And suppressing warnings with @ seems fishy to me.
The text was updated successfully, but these errors were encountered:
Trying out Grav on my Linux laptop. Ubuntu 18.04 LTS, php (7.2), nginx, php-fpm from system packages. Nginx config from webserver-configs directory with a modified server_name directive to match the website hostname configured in /etc/hosts.
When accessing http://mysitename.local/ for the first time, I get an exception with a stack trace.
session_start(): Setting option 'session.name' failed
The root cause is that
$options
arrays has keys withsession.
prefixes when invokingsession_start()
insystem/src/Grav/Framework/Session/Session.php
line 192. That is incorrect. The docs for session_start() explicitly say that$options
array should not havesession.
prefixes.Here is the array I get
I would have provided a patch but I am not yet familiar with the codebase. The patch I hacked works for me, but I need to learn how to run the test suite if Grav has one...
The error should have been caught by others but for some reason I am the person reporting it... And suppressing warnings with
@
seems fishy to me.The text was updated successfully, but these errors were encountered: