Any ideas how to elegantly resolve this problem? It's disconcerting to
people who install for the first time to be taken to the "First post"
straightaway.
--
GPG 9CFA4B35 | ski...@skippy.net | http://skippy.net/
If it's a case as freakerz says in comment #7 on this issue, that it's
using post.php instead of posts.php, isn't there some way to redirect
in a more "correct" way? This is similar to my long-time complaint
with wp (which I have to hack core to fix) where a subscriber logs in
and is taken to the backend - I really do NOT want that to happen
which is why I hack core - I want the person to be taken to the blog
main page not the backend. Here we want the person logging in to be
redirected to the normal blog main page, not to a single post page....
We really need some way for theme.php to figure out what kind of request
is currently being serviced. If it's a request for the home page -- no
query string, no HTTP POST, no nothing -- than the rule to trigger
individual post display ought not trigger. It's this that I'm asking
about, since I don't see how to do it at this time.
And speaking of default posts, wouldn't a default post(s) that had a
link to something useful,such as "getting involved" or a wiki page of
some sort be a better default than "first post" and "deleteme" tag?
Michael
Would a "sample" post and page accomplish the same thing? at least then
there'd be some logic behind two by default?
I'm +1 on the sample being something that points to something useful.