I manage a small site with 4 user groeps (anonymous, admin, authenticated and members).
After upgrading to the newest drupal version node-privacy byrole didn't work anymore
so I installed path acces.

I first tested the wildcards on a computer at university, where they seemede to work.
the path ?q=members was no longer available for auth. en anonym. users. and neither were the subpaths.
But when I got home to days later I tried this again to be sure and now even anonymous users can see the members pages.

1) If I use NO wildcards then the path members is CLOSED for anonym and auth, and the subpaths are OPEN to them.
2) If I DO use wildcards then both the path members and the subpaths are OPEN.

Can anyone help me out on this one?

greetings.

Comments

budda’s picture

budda
Primary language English
Location Cheshire
commented
Component: Miscellaneous » Code
Assigned: Unassigned » budda

Please try the dev build form august 2007 and report back if it still doesn't work.

anavarre’s picture

anavarre
Primary language French
Location 🇪🇺
commented

Confirmed with 6.x-1.0 (2010-Aug-30) and 6.x-1.x-dev (2011-Jul-23).

For instance, protecting all user/* paths will work ok (user/register or user/password) but access to "user" itself will be possible which is not the expected behavior.

budda’s picture

budda
Primary language English
Location Cheshire
commented

Works the same as setting what pages a Drupal Core block should appear on.
If you want to protect the 'user' url too - ie without a slash at the end then use the pattern:

user

budda’s picture

budda
Primary language English
Location Cheshire
commented
Status: Active » Closed (works as designed)