.. or just create a new permission for /node so that we can just block access to it.<br><br>~Rob<br><br><div class="gmail_quote">On Tue, Aug 11, 2009 at 11:32 AM, J-P Stacey <span dir="ltr">&lt;<a href="mailto:jp.stacey@torchbox.com">jp.stacey@torchbox.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">&gt;&gt; Some sort of glob- or regex-based URL locking-down,<br>
&gt;<br>
&gt; Contrib. hook_menu_alter. I mentioned already :)<br>
<br>
</div>Well, that hook&#39;s certainly one starting place. But it doesn&#39;t on its<br>
own solve the broader problem of how a non-developer could lock down<br>
more than just q=node.<br>
<br>
How about extending the access rules interface and system, and then<br>
using hook_boot() to call drupal_is_denied()?<br>
<br>
  <a href="http://code.torchbox.com/svn/drupal-modules/tags/ar_path/ALPHA-0.1/ar_path.module" target="_blank">http://code.torchbox.com/svn/drupal-modules/tags/ar_path/ALPHA-0.1/ar_path.module</a><br>
<br>
Cheers,<br>
<font color="#888888">J-P<br>
</font></blockquote></div><br>