I can't remember the last time I actually used /node. It's a great default for a fresh install and new users, but quickly becomes a problem for established users. I won't deny that a tiny contrib module would solve things, but it strikes me as the wrong solution. If I have to install a module that only does one menu_alter, then it really starts to sound like I'm having to work around a flaw instead of extending functionality. I don't think any of us want /node removed. We'd just rather have the ability to disable it, like we can with suggested menu items.<div>
<br></div><div>~Rob<br><br><div class="gmail_quote">On Tue, Aug 11, 2009 at 9:20 AM, Nathaniel Catchpole <span dir="ltr"><<a href="mailto:catch56@googlemail.com">catch56@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">Core can look if the system has any nodes at all , and only emit the welcome<br>
message if there are no nodes (not nodes promoted/published).<br></blockquote></div><div><br>The message isn't in Drupal 7 any more, or at least, not at /node, it's been replaced by a short message inviting you to add some content.<br>
<br>The real answer to this is the other thread on this list at the moment - views in core, so that the default front page (and default taxonomy, forum, blog and other listings) is just a view which you can enable, disable or modify.<br>
<br>Nat<br><br> <br></div></div>
</blockquote></div><br></div>