We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'll explain here an issue I found on TR editors but I guess we likely have similar cases with other disabled user or groups records.
While looking at unused accounts I noticed that some old editors accounts have been disabled, which introduce issues in the API.
Example "CC/PP exchange protocol" specification which was edited by "Hidetaka Ohto":
https://api-test.w3.org/specifications/NOTE-CCPPexchange/versions/19990624/editors lists Hidetaka Ohto as an editor but trying to follow his user record URI https://api-test.w3.org/users/fhlab53128occw4g8sgwg80g4wcw0ok?apikey=fvt9fms6qds8wkw88co4wscosookcck returns a 404 Not found error.
Hidetaka Ohto
404 Not found
I am not sure we can reactivate those user records as they were probably disabled for a valid reason, but the API should not lead to 404 links either.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'll explain here an issue I found on TR editors but I guess we likely have similar cases with other disabled user or groups records.
While looking at unused accounts I noticed that some old editors accounts have been disabled, which introduce issues in the API.
Example "CC/PP exchange protocol" specification which was edited by "Hidetaka Ohto":
https://api-test.w3.org/specifications/NOTE-CCPPexchange/versions/19990624/editors lists
Hidetaka Ohto
as an editor but trying to follow his user record URI https://api-test.w3.org/users/fhlab53128occw4g8sgwg80g4wcw0ok?apikey=fvt9fms6qds8wkw88co4wscosookcck returns a404 Not found
error.I am not sure we can reactivate those user records as they were probably disabled for a valid reason, but the API should not lead to 404 links either.
The text was updated successfully, but these errors were encountered: