Forums / Developer / Is policy basing its logic on main location only ?

Is policy basing its logic on main location only ?

« 
Previous topic
|
Developer
|
Next topic
 »
Author Message

Jerome Despatis

Friday 28 May 2010 8:15:23 am

Hi,

I've a section Restricted.

And an object that has a location in this section Restricted and its main location in another section (let it call anotherSection)

I'd like my user to see objects in this section Restricted, and as a result see this object.

So i've add a new policy: content/read/Section(Restricted)

=> But my user that are surfing in this section can't see this object !! The only ways I've found are:

* moving the main location of this object to this restricted section (but I don't want that)

* or adding a new policy content/read/Section(anotherSection), but I don't want that either...

Maybe I'm mistaken ? what is the solution ?

Thanks a lot for your help !

Jerome Despatis

Friday 28 May 2010 8:54:41 am

Arg, someone has IRC has confirmed me that section is attached at object level, and not at node level.

So my problem has no answer...

I have to put everything in the same section and try to limit by subtree...