When in doubt, well, don't ask... Think! Nothing comes up? Think harder!!!
There's something wrong with what I'm doing, and I don't think I did anything wrong.
I check, and check, and recheck... Everything seems to be in order.
I search for similar problems (i.e., google it), but nothing matches my "specific" case...
I sit back... I think: "What am I doing wrong? Am I missing something?"
"Hmm... Lately, I've been reading some bad reviews about that specific platform and stuff... Maybe it's the server that's the problem!"
...
"N'aahhh, there should be something with my code, some link that is not refreshing."
I get back into checking files, going through directories, listing permissions... Nothing.
"Aaagh! What's wrong with this stupid server!" ...(debugging continues)... "I mean, I reinstalled the whole base like 3 times already, and it's still NOT WORKING!!!
...(even more debugging occurs)... No result... Nothing, it's still refusing stubbornly to start up.
"Ok, that's it! I'm opening a case with the support! I can't take it anymore, they HAVE to fix it, it's THEIR job!!!"
I go to the "open a ticket" form, and start with the steps: Input information (blablabla...), did you try this (Yes!), did you try that (Yes!!), what about this (YEEESSS!!!), give us some info about that (blabliblou...). And then, I stop.
"Do you think?... No... It can't be! I mean, it's really silly, I don't think it's the problem. My problem is too importantly complicated to have such a simple/silly cause." ...(checking vigorously to see if the importantly-complicated problem has a simple/silly cause)... ":-$... Ahuh... Yup, that's the root of my frustration. Hehe, let's close that ticket form before submitting anything..." The root-of-the-importantly-complicated problem? A silly configuration file (ONE out of 2,902 files), with Read/Only attributes, that was not overwritten by the new (& many subsequent) installations. I fix it. I run. It works! "LoL, good thing I didn't file a ticket..."
So my conclusion is as my opening: "When in doubt, don't ask, think! And if nothing comes up, think harder."
Now, if after that you're still at square one (or zero), then document what you tried and then ask...
Because, if you need a fast answer, you need to spend some time preparing the question. A well prepared question will be surely quickly and (most important) accurately answered.
There's something wrong with what I'm doing, and I don't think I did anything wrong.
I check, and check, and recheck... Everything seems to be in order.
I search for similar problems (i.e., google it), but nothing matches my "specific" case...
I sit back... I think: "What am I doing wrong? Am I missing something?"
"Hmm... Lately, I've been reading some bad reviews about that specific platform and stuff... Maybe it's the server that's the problem!"
...
"N'aahhh, there should be something with my code, some link that is not refreshing."
I get back into checking files, going through directories, listing permissions... Nothing.
"Aaagh! What's wrong with this stupid server!" ...(debugging continues)... "I mean, I reinstalled the whole base like 3 times already, and it's still NOT WORKING!!!
...(even more debugging occurs)... No result... Nothing, it's still refusing stubbornly to start up.
"Ok, that's it! I'm opening a case with the support! I can't take it anymore, they HAVE to fix it, it's THEIR job!!!"
I go to the "open a ticket" form, and start with the steps: Input information (blablabla...), did you try this (Yes!), did you try that (Yes!!), what about this (YEEESSS!!!), give us some info about that (blabliblou...). And then, I stop.
"Do you think?... No... It can't be! I mean, it's really silly, I don't think it's the problem. My problem is too importantly complicated to have such a simple/silly cause." ...(checking vigorously to see if the importantly-complicated problem has a simple/silly cause)... ":-$... Ahuh... Yup, that's the root of my frustration. Hehe, let's close that ticket form before submitting anything..." The root-of-the-importantly-complicated problem? A silly configuration file (ONE out of 2,902 files), with Read/Only attributes, that was not overwritten by the new (& many subsequent) installations. I fix it. I run. It works! "LoL, good thing I didn't file a ticket..."
So my conclusion is as my opening: "When in doubt, don't ask, think! And if nothing comes up, think harder."
Now, if after that you're still at square one (or zero), then document what you tried and then ask...
Because, if you need a fast answer, you need to spend some time preparing the question. A well prepared question will be surely quickly and (most important) accurately answered.
