Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Bo Damgaard Mortensen 719 posts 1207 karma points
    Oct 07, 2011 @ 12:21
    Bo Damgaard Mortensen
    0

    Relate member to content

    Hi all,

    I'm having a bit of a blackout here when it comes to setting up member permission and relating members to content - I suspect I'm over-thinking it.

    I have the following structure:

    - Parent node 1
             - Child node
             - Child node
             - ....

    - Parent node 2
             - Child node
             - Child node
             - ....

    And in the members section I have a MemberGroup which has a MemberType. Upon registration on the frontend, I have a dropdownlist containing the Parent nodes which the client chooses from. This sets the selected Parent node on the Content Picker datatype on the member.

    So far so good, the member is now 'related' to the content he/she needs to be able to see. However, I don't want the member to be able to access any of the other Parent nodes except for the one he/she selected when registrating.

    So, the question is: how would you go about setting up access/permission with this structure? A simple if-statement would indeed tell me if the member is allowed to see the Parent node page (<xsl:if($currentPage/@id = contentpickerId">), but on the childnodes (and probably childnodes of childnodes) I will then have to check their parent for every page they're visiting. I just have a feeling that I've overlooked something to achieve what I want? :-)

    Any input is greatly appreciated!

    Thanks in advance.

    / Bo

Please Sign in or register to post replies

Write your reply to:

Draft