Custom menu's implemented in CMSMS / CustomContent

[Michail]

It would be great if a custom menu function could be implemented in CMSMS, that works with CustomContent.

I'm thinking of a page, where I can subscribe pages to a user, by checking some checkboxes. That would be great for beginners like me, with practically no knowledge of PHP!

[calguy1000]

I just thought of this today actually, and havn't tried it yet.  but it should be possible to do with the 1.0.x series.

The best way would be to prefix all of your private page aliases with _whatever, and all of your public pages with public_.

Then, you could use some smarty magic, and the custom content module within the menu manager templates to hide pages that were only available to members of certain groups.

I'd do it on a broad basis though, so if the parent page alias had group1_whatever, and the user was not a member of group1 then that entire menu would be hidden.  It'd be much simpler that way.

It's an adventure in smarty logic, but should be entirely doable as smarty does have some string processing plugins.

[richbothe]

Is there a way to limit content based on each individual user's login?  For example...

I have a an intranet site that contains training materials including the answers to quizes that managers will have access to.  These managers vary in what they're certified in and therefore can only have access to the answers of quizes of which they're already  certified.  The site also contains general material that all users need to have access to.  So far I have two groups.. Employees & Managers.

I was thinking of adding a form with checkboxes listing all content that would be restricted to user login, but I'm not sure how to incorporate that into the site or if there's a better way...

This project is moving quickly... I appreciate any input you may have.


Rich

[calguy1000]

This question about limiting content has been answered numerous times.

Here's the quick once over of how to do it with CMS Made Simple.

1. Install the FrontEndUsers, and CustomContent modules
2. Organize your pages such that all of the private content is located underneath a parent section header that is marked as "not shown in menu".  And pay attention to the page id (2.1, 3.1, 4.1...} of the first child of this section header
3. Put a second {menu ...} call in your page template surrounded by some customcontent logic.  kinda like this (your syntax may vary):

Code: Select all

{if isset($customcontent_loggedin) && $customcontent_loggedin > 0}
   {menu start_element='2.1' show_root_siblings='1'}
{/if}

Where '2.1' is the first child of your section header that is 'not shown in menu', and is usually your first private page.

Hope this helps.

[richbothe]

If I have several pages that need this {menu start_element='2.1' show_root_siblings='1'} then I need to setup separate templates for each separate page?