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
This newly registered speaker Priya Ananthasankar only registered a week ago but her profile seems to only exist under 21x. I think new users are being created under 21x instead of 22x or something isn't right. https://www.socallinuxexpo.org/scale/21x/speakers/priya-ananthasankar
The result is that she cannot see her submissions for 22x, when she logs in she just see:
Need to determine why this user (and potentially all new users) aren't able to see their submissions. Also need to fix this user and potentially all recently registered users once the fix is known.
The text was updated successfully, but these errors were encountered:
Hmm. Other users who have never spoken before are visible to CFP reviewers. Can't figure out why this one is different. If I "approve" her talk, the talk becomes visible to reviewers, but if I unapprove her we get the "not a speaker this year" message again.. Not sure what she sees in her account though.
This newly registered speaker Priya Ananthasankar only registered a week ago but her profile seems to only exist under 21x. I think new users are being created under 21x instead of 22x or something isn't right.
https://www.socallinuxexpo.org/scale/21x/speakers/priya-ananthasankar
The result is that she cannot see her submissions for 22x, when she logs in she just see:
She has 2 22x talk submissions she should be able to see:
https://www.socallinuxexpo.org/scale/22x/presentations/migrating-distributed-systems-infrastructure-serverless-methodology-and
https://www.socallinuxexpo.org/scale/22x/presentations/migrating-distributed-systems-infrastructure-serverless-model-methodology-0
Need to determine why this user (and potentially all new users) aren't able to see their submissions. Also need to fix this user and potentially all recently registered users once the fix is known.
The text was updated successfully, but these errors were encountered: