SOLVED Access levels on Gantry 5 templates
-
-
- RacerFX
- Sr. Rocketeer
- Posts: 175
- Thanks: 13
-
When you control all the content of a page using separate instances of the template, securing the content for use as an Extranet won't work. Yes, you can make menu items restricted to registered users, but I'm looking to allow the user to see the menu item, click on it and show that the page is restricted to registered users. So template driven content needs some sort of access control.
There looks to be another thread on this - Gantry request - Add Access and Permissions tabs
This also refers to a GitHub thread - Joomla Permissions for Gantry Particle in Modules
I'm not sure these requests are for the same reason as mine.
Is there a way to achieve this that I'm not seeing or should I make the request on GitHub? - Last Edit: 8 years 6 months ago by RacerFX.
-
-
-
- MrT
- Preeminent Rocketeer
- Posts: 101084
- Thanks: 13484
- Web Designer/Developer
-
I'm assuming you are asking this in the context of Joomla?
Joomla is in charge of permissions via ACL. You can put particles into a "Gantry 5 particle" module and then you can use Joomla ACL to control access to that module just like any other module.
Similarly if your menu item is accessing a component to which you don't have access then Joomla should redirect you to the login page.
NOTE: SEO extensions such as SH404SEF can interfere with the correct joomla behaviour - so if you have such a plugin disable it and clear cache so you can see the default Joomla behaviour first.
Regards, Mark. - Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
-
-
-
- RacerFX
- Sr. Rocketeer
- Posts: 175
- Thanks: 13
-
Mark,
I'm referring to the particles that only exist within a Template.
If I have a Gantry 5 Theme custom page, I'm not seeing any permission selection except for the menu item. Nothing within the template layout where these particle exist allow for ACL.
Normally, with the use of Single Article, where you can make the article protected, you can't do with a purely Gantry 5 Theme custom page.
Thanks for your help. - Last Edit: 8 years 6 months ago by RacerFX.
-
-
-
- MrT
- Preeminent Rocketeer
- Posts: 101084
- Thanks: 13484
- Web Designer/Developer
-
I must admit I never use the "custom page" Gantry 5 menu item to add particles as a component. It's better to have the particles in modules instead and then you can control access to them via normal joomla ACL. Putting a particle directly in the menu item means that the only access control that you have is to the menu item itself (not the content therein).
Regards, Mark. - Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
-
-
-
- RacerFX
- Sr. Rocketeer
- Posts: 175
- Thanks: 13
-
That's what I thought.
The client committed to setting up a number of pages based off the demo content. They then decided they wanted users to register before seeing any content beyond the front page. Hind sight, not the perfect setup and I'll figure another way to make it happen.
Thanks again.
-
-
-
- MrT
- Preeminent Rocketeer
- Posts: 101084
- Thanks: 13484
- Web Designer/Developer
-
It really should be as easy as:
1. remove the particle from the menu item itself
2. create the particle in a "Gantry 5 particle" module and assign to the menu item and a position on the page.
That should be it.
Regards, Mark. -
The following users have thanked you: RacerFX
- Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
-
Time to create page: 0.060 seconds