Download & Extend
Path Access » Issues

Disallow does not work (on certain paths)

Posted by Lausch on July 28, 2007 at 2:13am
Project:Path Access
Version:5.x-1.2
Component:Code
Category:support request
Priority:normal
Assigned:budda
Status:postponed (maintainer needs more info)

Issue Summary

hi this module seems not working.

i created a disallowing for

groups/*
groups
group/*
group

nothing works! user will correct role can just visit these pages.

greets

Lausch

Login or register to post comments

Comments

#1

Posted by hip on January 15, 2008 at 11:01am

Same happens to me with
node
node/
node/*

#2

Posted by budda on February 9, 2008 at 6:10pm
Assigned to:Anonymous» budda

Please try the dev build from August 2007 and let me know if this works for you guys.

#3

Posted by Leeteq on February 10, 2008 at 12:13pm

Subscribing.

#4

Posted by budda on August 15, 2008 at 10:49pm

Is this still an issue?
Just release 1.2 - let me know if you still experience bad behavior.

#5

Posted by lowkeynyc on October 16, 2008 at 6:41pm

I tired both builds and it doesnt work for me either on Drupal 5.

#6

Posted by jooel on November 10, 2008 at 10:43am

+1.

This doesn't work for me.

I am trying to restrict access to node/* for anonymous users without success (i only want them to access the alias). The module had no effect.

Restricting "front" worked though.

#7

Posted by budda on November 10, 2008 at 10:48am

The module takes any paths provided and converts them to their alias. If the alias is not listed, it wont protect visitors from that page.

#8

Posted by jooel on November 10, 2008 at 2:50pm

Ok.

I hacked the "globalredirect" module to accomplish what i needed, i e denying access to node/* and only allow aliases.

( in globalredirect.module change line 103 drupal_goto('$alias', $query_string, NULL, 301); to drupal_goto('', $query_string, NULL, 301); )

#9

Posted by Leeteq on November 10, 2008 at 6:58pm
Title:module not work!» Disallow does not work
Version:5.x-1.1» 5.x-1.2

@budda:
Please explain the rationale behind the disallow feature in regards to your comment in #7 here.

If I should guess, you are saying that first one has to create an alias, and only then can you get disallow to work towards that alias.

Does that mean that it only works with aliases you create yourself and which does not take part in existing paths that drupal core or other modules are implementing themselves? That paths such as "node" or "group" is not possible to "disallow"?

If so, I suggest adding such a statement to the readme and the project page, for clarification.

#10

Posted by Leeteq on November 10, 2008 at 7:01pm
Title:Disallow does not work» Disallow does not work (on certain paths)
Category:bug report» support request
Priority:critical» normal
Status:active» postponed (maintainer needs more info)

Maybe this is not a bug, but by design?

#11

Posted by budda on November 11, 2008 at 9:22am

@DanielTheViking The module attemps to convert any path to an alias if available.

$path = drupal_get_path_alias(check_plain($_GET['q']));

If no alias is found, the same path is returned as per the API docs.

So node* would work as a path to restrict.

The pattern matching code used is taken from Drupal cores block.module

nobody click here