remove automatic refresh when 'account not activated' message or similar is shown
in the past this was a common temporary issue with the intel site, so was worth having as a case in the code however, this is now very rare, and the more likely reason is an account suspension/ban - and a refresh won't help here!
This commit is contained in:
parent
26d410d306
commit
41979cb107
7
main.js
7
main.js
@ -39,8 +39,11 @@ if(!d) {
|
|||||||
// page doesn’t have a script tag with player information.
|
// page doesn’t have a script tag with player information.
|
||||||
if(document.getElementById('header_email')) {
|
if(document.getElementById('header_email')) {
|
||||||
// however, we are logged in.
|
// however, we are logged in.
|
||||||
setTimeout('location.reload();', 3*1000);
|
// it used to be regularly common to get temporary 'account not enabled' messages from the intel site.
|
||||||
throw("Page doesn't have player data, but you are logged in. Reloading in 3s.");
|
// however, this is no longer common. more common is users getting account suspended/banned - and this
|
||||||
|
// currently shows the 'not enabled' message. so it's safer to not repeatedly reload in this case
|
||||||
|
// setTimeout('location.reload();', 3*1000);
|
||||||
|
throw("Page doesn't have player data, but you are logged in.");
|
||||||
}
|
}
|
||||||
// FIXME: handle nia takedown in progress
|
// FIXME: handle nia takedown in progress
|
||||||
throw("Couldn't retrieve player data. Are you logged in?");
|
throw("Couldn't retrieve player data. Are you logged in?");
|
||||||
|
Loading…
x
Reference in New Issue
Block a user