Restricting access to specific pages

This support ticket is created 5 years, 1 month 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: Access plugin

This topic contains 2 replies, has 2 voices.

Last updated by Simon Logan 5 years, 1 month ago.

Assisted by: Shane.

Author

Posts

November 15, 2019 at 1:36 pm #1384227

Simon Logan

I'm trying to see what the best approach is to restricting access to specific pages based on the custom user roles created via Toolset Access.

I know that I can restrict access to creating, viewing and editing the custom post types I created using Toolset Access, however I believe the plugin can't restrict access to overall specific pages? I tried the "Restrict User Access" plugin however this seemed to thereafter remove the entire ADD form and EDIT buttons on an EDIT view which I'd created using Toolset.

Do you have any recommended approaches to blocking access to specific pages based on user role since it doesn't look like Access can do this?

November 15, 2019 at 2:46 pm #1384339

Shane

Supporter

Languages: English (English )

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

Hi Simon,

Thank you for getting in touch.

Actually our plugin can do this by using our post groups.

Have a look at the link below for how to set this up.
https://toolset.com/documentation/user-guides/limiting-read-access-specific-content/

Please let me know if this helps.
Thanks,
Shane

November 15, 2019 at 3:15 pm #1384375

Simon Logan

I managed to discover that Toolset could do just as Shane instructed shortly before his reply came through, I'd just been misunderstanding how that area of the plugin worked - thankfully Shane's response confirmed what I'd managed to do and I'm very happy that I can achieve this without the need for another plugin.