Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session handler change error #21947

Closed
twister65 opened this issue Sep 1, 2018 · 6 comments
Closed

Session handler change error #21947

twister65 opened this issue Sep 1, 2018 · 6 comments

Comments

@twister65
Copy link
Contributor

Steps to reproduce the issue

  1. Change Session Handler in PHP in the Global Configuration -> System -> Session Settings
  2. Save & logout
  3. Log in as Super User
  4. Change Session Handler in Database in the Global Configuration -> System -> Session Settings

Expected result

The session handler is database

Actual result

session error

System information (as much as possible)

systeminfo-2018-09-01T06_46_46-07_00.txt

Additional comments

@mbabker
Copy link
Contributor

mbabker commented Sep 1, 2018

Can you test this against the 3.9 alpha? There won't be another 3.8 release short of a security release or critical bug being found, and there were a couple changes to the session table schema in 3.9 which if I had to guess based on the "character varying" part of the error message should be fixed.

@mbabker
Copy link
Contributor

mbabker commented Sep 1, 2018

(Also for future reference, either copying in the actual error message or providing a translation if it's not in English would be preferred, that way someone can easily copy/paste the message into something like Google Translate if the message isn't in their native language or core's default English)

@twister65
Copy link
Contributor Author

I tested successfully (no error) with 3.9-dev branch.
Could you give the reference of the issue or the commit fixing this bug ?
Thanks a lot.

@mbabker
Copy link
Contributor

mbabker commented Sep 1, 2018

Probably #19708

@ghost
Copy link

ghost commented Sep 1, 2018

@twister65 if the Issue is solved please close it.

@twister65
Copy link
Contributor Author

Yes, the issue is solved (in 3.9), you can close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants