[2.x] Jetstream ignoring sessions from session connection in config #630
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When using Jetstream with the Livewire stack, It is impossible to use a second database connection specifically for sessions. As the component ignores the session.connection config value. Could also be fixed by allowing livewire components to be published from vendor folder. If It is possible it's an oversight on my part.
When using another database connection for sessions it is ignored in Jetstream
When retrieving user profile in Jetstream, it ignores a separate database connection for sessions
driesvints
changed the title
|
+1 thanks a lot - i just encountered this issue and was going to make a PR. I am 9 days too late- its your fame :) @sooand |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using sessions in a separate database connection, the sessions table is not found when querying or deleting sessions. This pull request takes the session.connection supplied in the config, so the session management for Jetstream can follow the users configs and/or .env values for session connection.
The changes has been made both for Inertia and Livewire stack.
Should be no breaking changes as it uses the same way Laravel/framework gets the session connection in the session manager: https://github.com/laravel/framework/blob/28e0f61bba1cbc727383d183b7116eb723de7660/src/Illuminate/Session/SessionManager.php
line: 99