2,562 reputation
1718
bio website
location
age
visits member for 3 years, 7 months
seen 42 mins ago

Jul
7
revised So I just got a Pottery Barn email that required I call the store to be removed
added 35 characters in body
Jul
7
revised So I just got a Pottery Barn email that required I call the store to be removed
added 391 characters in body
Jul
7
answered So I just got a Pottery Barn email that required I call the store to be removed
Jul
2
awarded  Curious
Jun
23
answered Error Log shows nosy visitors trying to access various admin pages
May
30
answered Panda 4: Reducing #indexed pages. How much is enough?
May
16
revised Why don't browsers respect cache headers for initial page request?
deleted 188 characters in body
May
16
revised Why don't browsers respect cache headers for initial page request?
added 178 characters in body
May
16
comment Why don't browsers respect cache headers for initial page request?
I've seen this before during debugging, but can't remember, is there a valid reason your response header shows Expires: Nov 1978? Or that may be your answer.
May
16
answered Why don't browsers respect cache headers for initial page request?
May
16
comment Low Bounce rate - too good to be true?
Thanks for the quick feedback.
May
16
answered Low Bounce rate - too good to be true?
May
12
comment Should I give preferential treatment to proxy users on my ecommerce site?
Quote: "A real user does not use proxy to visit any website" WHAT??
May
7
comment Moodle error - Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting.
You can put this in there also to make sure you see them all: error_reporting(-1);
May
7
comment Moodle error - Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting.
@Canadian Luke - inserting ini_set('display_errors', '1'); at the top of index.php will let you see the real errors but this being production could cause you security issues and usability problems.
May
7
revised Moodle error - Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting.
added 211 characters in body
May
7
revised Moodle error - Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting.
added 296 characters in body
May
7
answered Moodle error - Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting.
May
7
comment Moodle error - Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting.
I'll write it as an answer.
May
7
comment Moodle error - Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting.
Ya you would think that would be enough, it seems that you need to trace individual processes that are failing to the files they interact with and look at those files individually for problems. For example I've used some programs that create new log files at 777 even though I changed all existing log files to 600 after the fact.