Support » Plugin: Pods - Custom Content Types and Fields » Restricting read access of a pod

  • Resolved wvdw

    (@wvdw)


    We’re building a site containing several pods. Of one particular pod, we want to restrict read access with the effect that the pod is not public and only readable by registered and approved users. These users can – for example – mail us requesting read access.

    I am struggling to come up with the best approach. What would be a reliable and workable way to achieve this? Despite all published topics I can’t find a global approach to this so I am asking for some suggestions. Thanks for your input!

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jory Hogeveen

    (@keraweb)

    Hi @wvdw

    There are separate plugins for such a purpose like:
    https://wordpress.org/plugins/members/
    https://wordpress.org/plugins/restrict-user-access/
    https://wordpress.org/plugins/restrict-content/
    etc.

    Just search for “WordPress Restrict Content” and you’ll find plenty solutions for this.

    Cheers, Jory

    Thread Starter wvdw

    (@wvdw)

    Jory, thanks for taking trouble to answer. We ended up with the “members” plugin. That mission is accomplished. However, as posted here: https://wordpress.org/support/topic/pods-how-to-restrict-aceess-to-users/, setting up a pod for a limited group of writers failed. So we ended up with good old MoinMoin for that purpose. I would have expected it to be more straight forward and perceived the rights stuff as a bit fluffy. But then again, problem is solved.

    Plugin Author Jory Hogeveen

    (@keraweb)

    setting up a pod for a limited group of writers failed.

    What part failed? This is WordPress core, not Pods. Pods only allows setting this up through the UI. All the capability handling is done by WP core itself.

    Cheers, Jory

    Thread Starter wvdw

    (@wvdw)

    Off Topic, after all, “Restricting read access of a pod” is achieved…

    With the “members” plugin a role “coder” was made.

    Next we tried to assign only rights for maintaining an intranet pod with “developer_docs” for only “coder” users.

    We failed to do that in a straight forward way, probably overlooked something or suffered from lack of insights. We could give “coder” access but then it was site wide and assigning rights on a per page base was not considered as a useful option.

    Really appreciate your contribution, pointing out it is WP core, not pods clarifies it a bit. Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.