Skip Navigation

[Resolved] Toolset archive view doesn't respect Toolset Access rules

This support ticket is created 4 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 2 replies, has 2 voices.

Last updated by markW-21 4 years, 10 months ago.

Assisted by: Shane.

Author
Posts
#1666803

I am trying to: Display content in archive view according to Toolset Access rules

Link to a page where the issue can be seen: hidden link

I expected to see: list of items a user has access to

Instead, I got: No items found

I created an archive view for Series (custom type). I expected the archive view respects Toolset Access rules but it doesn't.
The post is a part of posts group X, the role Y has access to X posts group X and user Z has role Y.
But in archive view as a user Z I don't see any content.
User to test: toolset_user - you can change its password

#1667423

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Mark,

Thank you for getting in touch.

This is because the Post Group setting works on the individual post itself while the Archive is working based on the Permissions set on the Custom Post Type itself.

Essentially what is happening is correct. However if a user should navigate to the Post itself and the permission is set in the Post Group that doesn't give them access then they will be presented with the error.

The Post Group setting isn't applied on the archive pages.

Please let me know if this clarifies the issue for you.

Thanks,
Shane

#1667585

My issue is resolved now. Thank you!