Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
500 error page for user:me when not signed in
When searching, a user can be specified by including user:X
in the search term, where X
is the user id of the relevant user. You can also search for your own posts by specifying user:me
.
If you share a link to search results based on user:me
then the recipient of the link will see results for their own user, provided they are signed in. However, if they are not signed in they will see a 500 error page instead.
Could this 500 error page be replaced with something more informative, since we know the reason for being unable to display the results?
My ideal solution would be to inform the user that search results for `user:me` require a signed in user in order to kno …
3d ago
One option would be to display a message along the lines of: > Search results for `user:me` can only be displayed whe …
3d ago
In addition to whatever we do about the error, should we add a button/link/whatever for "share these results" on the res …
3d ago
I like both of Trichoplax's answers. I further submit that the HTTP response code should be 401 Unauthorized rather than …
3d ago
4 answers
In addition to whatever we do about the error, should we add a button/link/whatever for "share these results" on the results page? That way, if you meant to share your posts (specifically) with somebody else, you'd be able to do that without editing in your own user number. Sharing the URL re-evaluates "me", while this new link would be static.
One option would be to display a message along the lines of:
Search results for
user:me
can only be displayed when signed in. Please sign in and try again.
1 comment thread
My ideal solution would be to inform the user that search results for user:me
require a signed in user in order to know who me
refers to, and then show a sign in page that will automatically redirect to the search results once the user has finished signing in.
I understand this would be more development work than simply displaying a message, but since we already have the option of redirecting after signing in for other parts of the site, I mention this as a possible longer term feature.
0 comment threads
I like both of Trichoplax's answers. I further submit that the HTTP response code should be 401 Unauthorized rather than 5xx.
0 comment threads