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
In the status frontend, the UI could attempt to determine whether the current user has configuration errors, as another medium by which the user might discover the error.
This will be a lot easier said than done. It is possible but nontrivial to load the current user's username into an iframe, but the SCP Wiki forbids iframes on its site from transmitting information about the user, so using that value as part of a request is a non-starter.
Here's a couple of ideas:
A list of users with errors is part of the public log, which is downloaded into the frontend. If the current user is in that list, show the value.
It will not be trivial to add this data to the log, as it would be an entirely new field. I don't know if I want this data to be stored in the database even.
I suppose this field could just be a second public log, and would get uploaded as its own file during the maintenance stage.
Probably the minimal amount of information that needs to be downloaded.
http://notifications.wikidot.com/redirect-to-your-config exists to automatically send users to their own config page. The frontend could fetch that URL, follow redirects, and use the results to determine whether the user has errors.
This does not technically involve transmitting information about the user, although it does involve downloading information about them.
I have no idea whether this redirect actually works when initiated this way.
HTTP request probably doesn't work in an iframe loaded on a HTTPS site.
Uses more data than might be necessary (it will load at least 2 entire pages behind the scenes).
The text was updated successfully, but these errors were encountered:
Requires #46
In the status frontend, the UI could attempt to determine whether the current user has configuration errors, as another medium by which the user might discover the error.
This will be a lot easier said than done. It is possible but nontrivial to load the current user's username into an iframe, but the SCP Wiki forbids iframes on its site from transmitting information about the user, so using that value as part of a request is a non-starter.
Here's a couple of ideas:
The text was updated successfully, but these errors were encountered: