Fix - getEntitiesRestrictCriteria() returns invalid SQL criterion when no session is active#23934
Merged
cedric-anne merged 5 commits intoglpi-project:11.0/bugfixesfrom Apr 20, 2026
Conversation
…n no session is active
Merged
4 tasks
Contributor
Author
|
The initial problem is that |
Rom1-B
suggested changes
Apr 16, 2026
Rom1-B
approved these changes
Apr 17, 2026
AdrienClairembault
approved these changes
Apr 17, 2026
trasher
approved these changes
Apr 17, 2026
cedric-anne
approved these changes
Apr 20, 2026
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
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.
Checklist before requesting a review
Please delete options that are not relevant.
Description
When
getEntitiesRestrictCriteria()is called with no active session, no CLI context, and no cron context, the function falls through all conditions without an else branch. This leaves$valueas an empty string'', producing the invalid SQL criterionentities_id = ''on an integer column and triggering MySQL warning 1292 (Truncated incorrect DECIMAL value).This fix adds a missing else branch that returns
[new QueryExpression('false')]when no valid context is available, denying all access instead of generating invalid SQL. If there is no session, no results should be returned.Fixes all callers of
getEntitiesRestrictCriteria()that are affected by this edge case (e.g. pluginsGLPI/fields#1179).