dev/backdrop#8 - Move session start into CMS-specific classes. #23620
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.
Overview
Fixes https://lab.civicrm.org/dev/backdrop/-/issues/8 (or rather, a part of it; the rest is fixed by civicrm/civicrm-backdrop#159, which is a PR against a different repository).
Before
Previously, when
CRM_Utils_System::authenticate()
was called, it started a session. This creates warning messages in Backdrop CMS (though apparently not other CMSes). The solution is to move the session-starting code into CMS-specific classes and leave it out of the Backdrop-specific class.After
The session-starting code is now in the CMS-specific classes but not Backdrop. There was a suggestion in the comments (suggesting this exact change) that suggested it would not be necessary in the UnitTest class, so I did not put a copy of the code in that class.