February 25, 2026 at 6:07 pm
I have mentioned this several times over several years. Can someone please help me understand why this happens?
This morning I spent about an hour putting together some thoughts on the editorial regarding testing. When I was finished, I pressed the usual 'Submit' icon, and received the message to the effect 'Do you really want to do that' with the usual result that my comments completely disappeared. This has been a common and really irritating experience.
I'm on an Asus Windows 10 gaming laptop on which I actually run SQL Server, MSFT Office, financial software, internet interaction, etc. with an i9 64bit processor, 32gb memory, ethernet network is good and I don't have this problem with other sites.
Please give me an EXPLICIT explanation what happens to cause this. As is often the case in application development, and even database development, many problems are identified but not explained.
Rick
If you do a half-assed job of things, folks will ask 'why did this ass only do half the job?'
February 25, 2026 at 7:34 pm
Problem happens with me too. Best I can tell for me anyways is when I sit idle too long on the site in one or more tabs the problem happens. One difference though is that when it happens for me, it usually doesn't blow out my comment and I can just click to submit it again.
With DM's I have had it happen or worse - it looks like it went through but actually didn't. When that happens, I can OFTEN (not always) click on "back" and get my message back and resend it. Not sure if that applies to editorials or QOTD's or anything else as I haven't posted any of those - I stick to the forum or DM section of the page if I am posting anything.
I am not a site admin, but demanding an "explicit explanation" why a FREE forum has some hiccups is a bit entitled. It's very likely a server hiccup...
Also, I've worked in database and software development for a long time and I always try to root cause a problem. Treat the problem not the symptoms. Sometimes you treat the symptoms first so the business gets back up and running, but if you don't treat the root cause and explain it to those who need to know, it'll just happen again. I had a server a few months back suddenly hit a massive blocking issue and took down the primary app for that database. I looked into it treated the symptom (killed the process that was blocking) and then root caused it (user had done a cross join against 3 large tables).
I wouldn't say "often the case" when I've actually found the opposite - when problems are identified, they are assessed to determine if it should be an immediate remedy with future root cause OR if root cause should occur first. As an end user, you sometimes need to dig for the root cause as most non-technical people don't care what caused the problem, they just care that it is fixed. If you see that problems are identified but no root cause is presented to you, you might not be looking hard enough or asking the right people...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply