Skip to content

Conversation

@GuySartorelli
Copy link
Member

It's best practice to avoid using deprecated code where possible, but sometimes it's unavoidable. This API will all continue to be available at least until the next major release.

- The [`Session.session_store_path`](api:SilverStripe\Control\Session->session_store_path) configuration property has been deprecated. Use `session.save_path` in ini configuration instead.
- The [`Session.session_store_path`](api:SilverStripe\Control\Session->session_store_path) configuration property has been deprecated. Use [`session.save_path`](https://www.php.net/manual/en/session.configuration.php#ini.session.save-path) in ini configuration instead.
Copy link
Member Author

@GuySartorelli GuySartorelli Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This link should have already been there


When using the `FileSessionHandler` save handler the [`open_basedir`](https://www.php.net/manual/en/ini.core.php#ini.open-basedir) PHP configuration option can cause problems. If that option has a value set, the location where session files are saved (defined by [`session.save_path`](https://www.php.net/manual/en/session.configuration.php#ini.session.save-path)) must be within a directory declared in `open_basedir`. Otherwise session functionality won't work.

Note that including the sessions diretory in `open_basedir` will allow any PHP code to interact with files in that location. If you don't want that to be the case, you can do one of the following:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note that including the sessions diretory in `open_basedir` will allow any PHP code to interact with files in that location. If you don't want that to be the case, you can do one of the following:
Note that including the sessions directory in `open_basedir` will allow any PHP code to interact with files in that location. If you don't want that to be the case, you can do one of the following:

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@GuySartorelli GuySartorelli force-pushed the pulls/6.1/cant-interact-with-sessions branch from 1b274b0 to e644425 Compare January 15, 2026 20:33
@emteknetnz emteknetnz merged commit f7daf4e into silverstripe:6.1 Jan 16, 2026
3 checks passed
@emteknetnz emteknetnz deleted the pulls/6.1/cant-interact-with-sessions branch January 16, 2026 03:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants