Issue #3085803 Added conditional check to account object to be null. #1533
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
jaapjan
added
bananas
type: bug
jaapjan
pushed a commit
that referenced
this pull request
Oct 8, 2019
…al_profile_privacy_form_alter (#1533)
ronaldtebrake
changed the title
ronaldtebrake
added
verified-cherry-picks
|
Also in 6.4 |
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.
Problem
In social_profile_privacy_form_alter(), $account is not checked for being NULL when the parameter user is not found in URL. This blocks any user to edit profiles.
Solution
Add a null check.
Issue tracker
https://www.drupal.org/project/social/issues/3085803
How to test
Release notes
Introduces an empty check in social_profile_privacy_form_alter in social_profile_privacy module.
Change Record
N.A