[development] Remove q=node from required modules

[Karoly Negyesi]

Quite close. I was thinking on the bus about this and I thought
'access content listings'.

On Tue, Aug 11, 2009 at 12:00 PM, Robert
Wohleb<rwohleb at techsanctuary.com> wrote:
> .. or just create a new permission for /node so that we can just block
> access to it.
>
> ~Rob
>
> On Tue, Aug 11, 2009 at 11:32 AM, J-P Stacey <jp.stacey at torchbox.com> wrote:
>>
>> >> Some sort of glob- or regex-based URL locking-down,
>> >
>> > Contrib. hook_menu_alter. I mentioned already :)
>>
>> Well, that hook's certainly one starting place. But it doesn't on its
>> own solve the broader problem of how a non-developer could lock down
>> more than just q=node.
>>
>> How about extending the access rules interface and system, and then
>> using hook_boot() to call drupal_is_denied()?
>>
>>
>>  http://code.torchbox.com/svn/drupal-modules/tags/ar_path/ALPHA-0.1/ar_path.module
>>
>> Cheers,
>> J-P
>
>