Reading exceptions – setup and hierarchy

  • Resolved rattenkind

    (@rattenkind)


    11 years, 6 months ago

    Hi,

    I would like to restrict access to certain pages/posts only to certain subscribers (either to hand-picked individual users, or to only certain defined user groups).

    So such a restricted post should be

    -inaccessible to subscribers
    -unless they are explicitly granted access (individually, or through group membership)
    -accessible to administrators

    I’m a bit confused how to set this up. Using the reading exceptions panel, if I set on the ROLE tab “subscriber” to blocked, and then on the user tab a specific subscriber to “enabled”, which setting takes precedence?
    Does username beat group membership, which beats role?

    Also, I noticed that when a page is restricted that way, NEW subscribers do NOT get the reading exception assigned (at least it doesn’t show up in the backend user list in the exceptions column). This obviously ruins the functionality.

    So how do I set this up to get the desired behavior?

    Thank you!

    https://ww.wp.xz.cn/plugins/press-permit-core/

Viewing 1 replies (of 1 total)
  • Plugin Author Kevin Behrens

    (@kevinb)

    11 years, 5 months ago

    The best practice is to set those posts to give those posts a visibility of Private (using the WP publish metabox). Then use Reading Exceptions to enable desired roles, groups and/or users. Assigning an exception to a role does not cause a user-specific exception to be assigned at new user creation. The assignment is directly to the role.

Viewing 1 replies (of 1 total)

The topic ‘Reading exceptions – setup and hierarchy’ is closed to new replies.