In my defense, I've had a lot going on the past few months,
-raybeere
Understood. No shame in that.
But this left me puzzled so I got to thinking...
I think with Firebug it didn't actually load
anything which is why it displayed a blank from within the calling page. You asked for a non-existent (under Linux naming convention rules) element and it displayed what it found. In this case nothing - as in
null. Which isn't
quite the same thing as a blank page - which
is technically something. Maybe it creates an empty file on the fly if it can't locate the one being requested?
A "stylesheet not found" error message would have been a lot more helpful, but whatcha gonna do?
Stuff like that happens to me all the time. I can successfully troubleshoot the most bizarre Windows server problem over breakfast. But then I'll make the dumbest typo imaginable for a common command in a two line script I've written before lunchtime. Or fix something really complex, run a test, catalog the fix, archive a copy, pop it on a USB key, invoke it on the live machine as a final test and verify it works there - and then forget to write the changed file to disk
on the machine it's supposed to run on. After the script's termination, or following the next reboot, the
old script loads and the problem I just "fixed" is back. And I'm sitting there like a dork thinking "Swell! What
else just broke?"
Happens to all of us.
Try not to think about it too much.
Hope you're feeling better!
Recent PostsWell done! And laughter is a great way to deal with otherwise angering topics.
-Renegade (November 09, 2012, 05:49 AM)
