fix: Space created by non admin results to not found page - MEED-10255 - Meeds-io/meeds#4053#129
Merged
sofyenne merged 1 commit intofeature/meeds-qauifrom Feb 17, 2026
Merged
Conversation
|
sofyenne
added a commit
that referenced
this pull request
Feb 17, 2026
…- Meeds-io/meeds#4053 (#129) Prior to this change, creating a new space with a simple user redirected the user to the Not Found page, making the space inaccessible. The issue occurred because the role was not properly fetched due to the request lifecycle transaction not being restarted. This update restarts the transaction after the membership update, ensuring the role is correctly retrieved and resolving the issue.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Prior to this change, creating a new space with a simple user redirected the user to the Not Found page, making the space inaccessible. The issue occurred because the role was not properly fetched due to the request lifecycle transaction not being restarted. This update restarts the transaction after the membership update, ensuring the role is correctly retrieved and resolving the issue.