probably bug in dev for subselector with roles

[Frank Vèssia]

I don't know where to post this...
Maybe I found a "bug" using this selector

$pages->find("template=picture,image.count=2,limit=10,parent=[pagefield1.pagefield2=xxx]");

What happend here is it I call this selector from an url segment like /photos/new-users/ where "new-users" is the segment. If I'm logged in with admin role I can see the result, otherwise (other role or guest) not. I already checked all my roles and they are ok with permissions, and removing the subselector get me the result for every role or guest. It's something related with this subselector and roles I guess...any idea? 
I'm using latest dev 2.5.14

pagefield1 is a pagefiled connected with user template.
pagefield2 is normal pagefiled.

Edit: removing the urlSegment1 doesn't affect the result, so it's roles/subselector

Edited January 22, 2015 by Sevarf2

[Frank Vèssia]

any idea how to workaround on this?

[Soma]

Don't know really. But guest or normal users usually don't have access to "user" pages/template. Either give them view access to "user" or try add a "check_access=0".

[Frank Vèssia]

mmm i tried, same result, because i'm not trying to access to users page, i'm searching for "picture" template and trying to filter by user typology. Picture template ahs a parent which is the Profile page, this page has a page filed connected to user, user has a typology field, this is i'm filtering by.

[Soma]

I'm not even sure I understand the what where and how. But I'm sure if a user has no access to user template or roles you can't filter with subfields. I recognized this in ListerPro too.

Edit: Also, "I tried" doesn't say anything to me. 

[Frank Vèssia]

 probably I confused a bit but yes it's a problem of access...I'll figure something else for this
 

edit: oh easy, I just granted access "view" to user template to a specific role, now it's working, thanks Soma