-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to find my username in DOK search. #27
Comments
Update! I changed the setting to "Let anyone see my decks and user stats" and that fixed the search issue after a few minutes. I sent the bug report prior to it taking effect. But I'm not sure if the messaging is a separate issue that would be impacted by that setting. |
Yeah, that's definitely why they couldn't find you. (Note you can share your profile for them to leave reviews from the my DoK page. There is a link there.) The messages thing is weird though and unrelated. I'd need more info from them about how to troubleshoot that, like what page they sent the message from, did it show in their sent messages, etc. |
Hi Nathan,
Thanks for getting back to me. I'll make sure to either leave the setting
on or send them the link :)
I'll contact the buyer to see if they're willing to take the time to do
that. Thanks for your time!
All the best,
Ben
…On Thu, May 27, 2021 at 4:37 PM Nathan Westlake ***@***.***> wrote:
Yeah, that's definitely why they couldn't find you. (Note you can share
your profile for them to leave reviews from the my DoK page. There is a
link there.)
The messages thing is weird though and unrelated. I'd need more info from
them about how to troubleshoot that, like what page they sent the message
from, did it show in their sent messages, etc.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUIAVG5YG622JPMF56CRUV3TP2USFANCNFSM45VARQIQ>
.
--
[image: photo]
*Benson Zhou*
Chiropractor, Massage Therapist, Entrepreneur
289-597-5539 | 647-962-6212
www.vigorhealthandrehab.com
<http://facebook.com/dr.bensonzhou> <http://linkedin.com/in/dr-benson-zhou/>
<http://twitter.com/BenZ_Chiro>
Create your own email signature
<https://www.wisestamp.com/create-own-signature/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=>
|
the only proof I can provide that I sent a message in DOK about purchasing the deck is a screenshot from my email. I’m new to GitHub, any idea how I post the picture here? |
Figured it out |
Thanks day2424, I can't actually see the image, but maybe it's still uploading? |
This is not for reporting problems with the SAS or AERC rating of cards / decks! Use the Card change report template for that.
Describe the bug
Both another user and myself (using incognito mode) were unable to find my username (ChaosChrno) in the User search on DOK. The user was going to write a review for a recent sale but wasn't able to see my username for the purchase. The user had said they sent messages through DOK prior to emailing me but I didn't receive them either.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected my username to show up on searches. I'm not sure if any other function related to my account is affected as I have never made a purchase before.
Screenshots




Attached.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Nothing else. Thanks for your attention on this matter!
The text was updated successfully, but these errors were encountered: