You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the simple act of changing the screen name in the user profile will cause the user's private project to become invisible. Returning the screen name in the user profile to the original screen name will restore access to the user's private projects.
The text was updated successfully, but these errors were encountered:
I was able to identify code in the UserService and UserDao layers that are using the Blockly user ID and screenname as a compound key to identify project ownership. When the user changes the screen name in their profile, it essentially removes the existing linkages to private projects. Working on an update that will remove the compound key.
This is also related to #1649 in that updating the screen name in the user profile was not updating the screen name in the blocklyprop user table. This then created a screen name mismatch, which broke the query that was listing the user's private projects based on a combination of the user id and the user's screen name.
The second update to this issue is not done. The immediate workaround was to simply disable the feature that supported changing a screen name in the user profile. We still need to add code to fix what is actually broken.
It appears that the simple act of changing the screen name in the user profile will cause the user's private project to become invisible. Returning the screen name in the user profile to the original screen name will restore access to the user's private projects.
The text was updated successfully, but these errors were encountered: