About the access right issue

  • Resolved annielaw

    (@annielaw)


    2 years, 3 months ago

    In the previous version, I uncheck the “Publicly Queryable” which not allow the direct access to the specific post and will redirect to the main page. In the new version of Pod, if I uncheck the “Publicly Queryable” the content will be set as private and not display for visitor.

    I use a lot of Pod in my website like for our company staff information and I want to have a list page to display their information and no need to have detail page for them.

    I don’t know how the new version Pod can do the some thing as I previous use?

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

    (@keraweb)

    2 years, 3 months ago

    Hi @annielaw

    The extra information on public vs private is just a more detailed explanation on how content is handled. In case it’s private you can still create your overview pages, the only thing is that these CPT do not have a detail page.

    I believe in your case no action is needed. Since the WP registered post type stays the same, it’s functionality most likely as well.

    Cheers, Jory

    Thread Starter annielaw

    (@annielaw)

    2 years, 3 months ago

    May be I try to describe my problem using some example.

    I have a pod called people with job position, email, office location etc…and title is their name.

    I list this information like a table with 2 columns.
    Mr. Brown Mrs. Smith
    email email
    office location office location

    In the previous version, if I check the “Publicly Queryable” and I try to type https://mydomain.com/people/mr-brown it will show a page with the title only but if I uncheck the “Publicly Queryable”. It will go to my website front page.

    In the updated version, if I uncheck the “Publicly Queryable”. The visitor without login can see the content of the page. When I check the “Publicly Queryable” then people can search / access the detail page by the direct link of the pod (like the link I show in the previous paragraph)

    • This reply was modified 2 years, 3 months ago by annielaw.
    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    2 years, 2 months ago

    Public vs Private is just part of the big picture in Pods 3.1+ — you can now customize Access Rights when editing your Pod using the “Access Rights” tab.

    You can also go to Pods Admin > Access Rights Review and look at the Content Visibility setting there for that custom post type that you are embedding.

    If you set it to Public OR Enable Dynamic Fields (not using the WP Default) then that should get you where you need to be. If your Restricted Dynamic Features are set to Display and Forms, then you may want to unrestrict Display if you still want a non-public content type and it’s fields embeddable.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘About the access right issue’ is closed to new replies.