- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Frist
Admin
Frist
Admin
Geez, that captcha reads TV. I would know, I'm an AI.
Yes, I did check "I'm not a robot". Yes, I did lie.
Admin
wait... Super hardened win check child? What? Yes that is the first error message here, please do keep this to yourself. Lawsuits could commence. Did no body proofread these error messages?
Admin
I'm actually surprised that Jan (oh hey, yet another one with that name! How's it going?) managed to actually use the Media Markt site successfully, and even managed to buy something. I always found that site to be a pain in the ass to use.
Admin
You can have all the jquery you want... after the revolution.
Admin
Your pathetic attempt at a captcha was clearly foiled by Zorro himself.
Admin
Maybe I've been dipping to often into the JavaScript Kool-Aid but that error made perfect sense to me. For those not yet initiated, the erroring js library must be injecting jquery when being stood-up. If jquery is later initialized, it borks up our lib under inspection. Praise be to order-dependent #includes! It is telling you to either configure the lib to not inject jquery itself or to remove the future, unneeded reference to jquery.
Admin
@anonymous javascript initiate: You do realize that to a non-computer person, not one word in that explanation made any sense.
Admin
It should have been tested and fixed by a computer person before any non-computer person saw it.
("X is happening twice. X is supposed to only happen once. Here are two different ways to fix it, figure out which is better in your case.")
Admin
So... that first one... Hardened failed trying to get into virtual box right?
Admin
Not all error messages is intented for non-computer persons.
Admin
But officer, the child was hard, not me!
Admin
And that's exactly the WTF! The message itself may be fine (I have no idea), but showing it to the user is annoying to the user and not helpful to the developer. I never understood why so many web frameworks do this, instead of dumping the message to a log or wherever the dev can read it, and showing the user a generic error message like "We're sorry blah blah your request could not blah blah please try blah blah blah (won't help; just to keep you busy) ...".
Admin
"This error should never happen." No shit shirlock, but maybe you aren't as great of a programmer as you thought you were!
Admin
The CAPTCHA is so obscure that is clearly an anti-CAPTCHA, as is, only bots will try and manage to solve it
Admin
I have once upon a time written a "this should never happen" error message box. As a newbie I had never thought that a vendor of 3rd party library could actually add new values to an enum returned by a function.
Admin
Blech. Zoho is mediocre at best, brought to you by the people who make spaghetti power-line monsters and call it public infrastructure, as well as buildings that like to collapse.
Admin
Error messages from a production server to a visitor certainly ought to be intended for the visitor. Especially when the message suggests that the visitor try a couple of things to fix the problem.
Oh, and the captcha is obviously 立.
Admin
Actually, gibberish-gibberish-e-7 GB is somewhere in the kilobyte range. You already are out of space, which might be the reason for the garbled display. That plus not using decimal number formatting in the first place.
Admin
The author of the error message (the creator of this "revolution slider" thing) obviously didn't intend for it to be shown to visitors on a production server, duh.
Admin
I had the sad thought that it was a CAPTCHA loaded as two separate images.
Admin
Part of writing robust production-ready controls is ensuring messages that could potentially be seen by an end user provide some sort of value to that end user. Messages that provide value to developers should be written to console, logs, etc. As already advised by Foo.
Admin
Or, you could write the message somewhere where the average developer might have a chance of actually seeing it. Admittedly in this case we seem to have a below-average developer....
(Also, if you're going to be snarky about what other people have "already" posted, you might want to remember that comments are sometimes hidden for moderation and not visible immediately.)
Admin
I once gave my friend an elephant to keep in his room. He thanked me, so I told him "don't mention it".
Admin
Fair point.