Download & Extend
Path Access » Issues

Problems with paths with + and urlencoded non-English characters

Posted by solipsist on August 28, 2006 at 9:25pm
Project:Path Access
Version:5.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:budda
Status:postponed (maintainer needs more info)

Issue Summary

Paths such as profile/profile_field/alpha+beta+gamma or paths with URLencoded strings such as profile/profile_class/g%C3%A5r+i+klass+4 (for us who run non-English sites) are not protected even with patterns such as profile/profile_class* and similar.

Login or register to post comments

Comments

#1

Posted by budda on September 17, 2006 at 11:27pm

What do you mean by "not protected" ?

#2

Posted by solipsist on September 18, 2006 at 10:31am

You can't deny access to paths that contain anything but basic alfa-numeric chars. I.e. they are not protected since path access can't block access to them.

#3

Posted by budda on February 9, 2008 at 6:35pm
Version:master» 5.x-1.x-dev
Assigned to:Anonymous» budda

Can you make Drupal blocks appear/disappear form the same type of urls?
The path_access module uses the same code as Drupals block visibility system.

#4

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

Subscribing.

#5

Posted by solipsist on February 11, 2008 at 10:36am

I'll have to take a new look, it's been almost 18 months since I last tried this.

#6

Posted by budda on December 25, 2009 at 12:18am
Status:active» postponed (maintainer needs more info)

Any update on if these rules were possible on Drupals block system?