Forums keep locking me out - Downloaded from the Wizards Community, all coding removed by Solauren

Forums keep locking me out

Post/Author/DateTime Post
#1
celloshane
Apr 09, 2009 12:01:14 Ok, I'm understanding about the issue with subscriptions, it doesn't bother me in the least. The viewing issue, where I have to refresh multiple times before I can see a thread, is annoying but I'm aware it's a known issue. However, somewhere in this process I occasionally get an error saying I don't have permission to view a page. This has happened 3 or 4 times within the last hour. When this happens I have to log out, close my browser, reopen and log in again before I can view properly. If I vary from those steps at all I get the same error. I'm using IE7. Is this a known issue and if so is there a workaround, or do I need to report this to customer service?
#2
Zherog
Apr 09, 2009 12:41:44 You actually don't need to log out and log in. You just need to wait for them to fix the permissions so you can view things again. It's just a coincidence that it's resolved after you log out and log in.
#3
celloshane
Apr 09, 2009 13:44:24 So it's a matter of active changes and waiting for resolution?
#4
ORC_Sinister
Apr 09, 2009 21:01:26 Hey Guys,

As it was pointed out it's a matter of just waiting and trying to reload the page. Every once in awhile it happens to me as well.
#5
celloshane
Apr 10, 2009 8:27:09 Thanks for the clarification Z-man, Sinister.
#6
Zherog
Apr 10, 2009 10:02:01 Also note that how long it takes is pretty much related to when it happens. Yesterday, for example, it happened during normal business hours. Because of this, it was resolved pretty quick - the techs are already in the office, so it's just a matter of running the script against the database to correct it.

A few weeks ago, it happened on a Sunday. That time it took several hours for it to come back. And that makes sense, too. Customer Service (I'm assuming they'd be the first to know about it) would need to page/call somebody on the tech team. That person would need to get into the system (either remote access if they have it, or going into the office if they don't), and then run the script to correct the issue.

It'd be awesome if they could figure out the problem. But sometimes, finding a problem in a database is worse than finding a needle in a haystack.
#7
Paulon
Apr 11, 2009 0:04:27
It'd be awesome if they could figure out the problem. But sometimes, finding a problem in a database is worse than finding a needle in a haystack.

At least with a needle in a haystack you can use a metal detector, or burn the hay and sift the ashes. I've been tempted to suggest the latter option when the bug hits too often... ;)

Post/Author/DateTime	Post
#1 celloshane Apr 09, 2009 12:01:14	Ok, I'm understanding about the issue with subscriptions, it doesn't bother me in the least. The viewing issue, where I have to refresh multiple times before I can see a thread, is annoying but I'm aware it's a known issue. However, somewhere in this process I occasionally get an error saying I don't have permission to view a page. This has happened 3 or 4 times within the last hour. When this happens I have to log out, close my browser, reopen and log in again before I can view properly. If I vary from those steps at all I get the same error. I'm using IE7. Is this a known issue and if so is there a workaround, or do I need to report this to customer service?
#2 Zherog Apr 09, 2009 12:41:44	You actually don't need to log out and log in. You just need to wait for them to fix the permissions so you can view things again. It's just a coincidence that it's resolved after you log out and log in.
#3 celloshane Apr 09, 2009 13:44:24	So it's a matter of active changes and waiting for resolution?
#4 ORC_Sinister Apr 09, 2009 21:01:26	Hey Guys, As it was pointed out it's a matter of just waiting and trying to reload the page. Every once in awhile it happens to me as well.
#5 celloshane Apr 10, 2009 8:27:09	Thanks for the clarification Z-man, Sinister.
#6 Zherog Apr 10, 2009 10:02:01	Also note that how long it takes is pretty much related to when it happens. Yesterday, for example, it happened during normal business hours. Because of this, it was resolved pretty quick - the techs are already in the office, so it's just a matter of running the script against the database to correct it. A few weeks ago, it happened on a Sunday. That time it took several hours for it to come back. And that makes sense, too. Customer Service (I'm assuming they'd be the first to know about it) would need to page/call somebody on the tech team. That person would need to get into the system (either remote access if they have it, or going into the office if they don't), and then run the script to correct the issue. It'd be awesome if they could figure out the problem. But sometimes, finding a problem in a database is worse than finding a needle in a haystack.
#7 Paulon Apr 11, 2009 0:04:27	It'd be awesome if they could figure out the problem. But sometimes, finding a problem in a database is worse than finding a needle in a haystack. At least with a needle in a haystack you can use a metal detector, or burn the hay and sift the ashes. I've been tempted to suggest the latter option when the bug hits too often... ;)