- Joined
- Apr 11, 2009
- Messages
- 49,310
- Reaction score
- 7,207
- Points
- 2,244
- Location
- Greensboro, NC
- Military Branch
- Alma Mater
I couldn't resist channeling my inner Britney ...
Since opening the new site, we've experienced an odd little glitch. Sometimes, when replying to a thread, sending a message, or starting a new thread, we've seen 'Oops... something went wrong' messages popping up. Most of the time, simply refreshing and trying again works. Sometimes not. Either way, we obviously want you to be able to use all the site functions without getting error messages. We've seen the 'Oops' warning on desktop use and when using a phone or mobile device.
After discussing with our server host and our Sucuri firewall support, we've made a small setting change. We think this may resolve the issue but since the problem is intermittent, we need your help. If you all could report any instance of the 'Oops' message and also let us know specifically what you were doing when you saw it (replying to a thread, etc..), that would be very helpful.
Thanks in advance for helping us confirm we've either resolved that bug, or helping us track it down if needed!
Since opening the new site, we've experienced an odd little glitch. Sometimes, when replying to a thread, sending a message, or starting a new thread, we've seen 'Oops... something went wrong' messages popping up. Most of the time, simply refreshing and trying again works. Sometimes not. Either way, we obviously want you to be able to use all the site functions without getting error messages. We've seen the 'Oops' warning on desktop use and when using a phone or mobile device.
After discussing with our server host and our Sucuri firewall support, we've made a small setting change. We think this may resolve the issue but since the problem is intermittent, we need your help. If you all could report any instance of the 'Oops' message and also let us know specifically what you were doing when you saw it (replying to a thread, etc..), that would be very helpful.
Thanks in advance for helping us confirm we've either resolved that bug, or helping us track it down if needed!