I have been working tirelessly on figuring this out. I installed a test install of SilverStripe (latest version, of course) and was fiddling with it. I managed to learn a few things that may help someone help me, but frankly this is getting pretty ridiculous. I am to the point where I consider writing an entire CMS from scratch to be a more elegant (and much faster) solution. Who do you have to kill to get a little help around here? It seems this is a stupid newbie question that should be answered in a couple sentences. (So I would appreciate no suggestions to go pay $150/hr. to talk on the phone with a SilverStripe support specialist. I'm not here to burn cash. This should be really, really simple.)
I created a fresh install of SilverStripe. Everything was in working order. I applied the blog module, ran /db/build?flush=1, and the blog module works perfectly within the CMS. However, once again, when going to /blog/ nothing appeared.
I did, remarkably, discover that going to /blog/sample-blog-entry/ actually turned up the exemplary blog entry!! Unfortunately, I was not able to discern why it did NOT work at the main /blog/ module page. My suspicion is that there is some kind of problem with the PHP in /blog/code/, but that's a (poorly formed) hypothesis, at best.
Interesting to note, I re-installed SilverStripe over again including the blog module from the get-go, and what actually ended up happening is that the home page of my SilverStripe install ALSO began behaving like the /blog/ module previously (with a completely blank page, and no errors of any kind). The subsequent (About, Contact, example pages) did not encounter this problem. Furthermore, the /blog/ module's main page also continued to misbehave by producing a blank page. However, what is very curious is that if I go to /?stage=Live, everything works fine, but this benefit is not extended to the /blog/ module (i.e. /blog/?stage=Live still produces a blank page).
My guess is that, based on this behavior, the problem is most likely stemming from the /db/build?flush=1 program that, when the blog module is installed, some database corruption occurs, because this problem is isolated to the blog module itself if I install the blog module *after* installing SilverStripe; this problem exists on the SilverStripe root directory if I install SilverStripe and the blog module simultaneously. Does this bring anyone closer to the clues?
As you can see, I have spent many hours (needlessly) diagnosing this problem. I am not sure why it is only happening to a few people, but it is a pain in the ass. If it a configuration issue, the only thing that it could be (according to the SilverStripe installation program) is mod_rewrite, which it can't tell is enabled. I have it installed on my server and SilverStripe works fine, so my assumption is this is not the issue.
Help would be appreciated.