1. Our current site --- www.mtlfd.org has a public section that we can very easily control via CMSMS.
2. We want to add a members section that you must sign into. I'd like to be able to control access by adding a username/password for each and every member of our department.
3. I want a number of subpages (like the current public site) under this new Members section that can only be seen once you have logged in. If you are not logged in, all you see is Members in the left-hand menu.
There HAS to be a way to do this. A few people tried to help me before in another thread (http://forum.cmsmadesimple.org/index.ph ... 611.0.html) but unfortunately things got stuck and I'm back to square one here.
I WANT TO PAY YOU FOR YOUR HELP. I really, really want to make this work and I'm hoping there's someone out there that can help me figure this out once and for all. I've really liked using CMSMS but I don't want to abandon it because we can't easily use it and have a members section as well.
If you can help me, PLEASE contact me ASAP via this posting or my personal email at josephpolk@yahoo.com. Thank you in advance for replying to this posting and helping me and our department!
Desperately need help creating a members section!
-
josephpolk
- Forum Members
- Posts: 11
- Joined: Wed Jul 09, 2008 5:10 am
Re: Desperately need help creating a members section!
I have done exactly what you are wanting to do.
You need the combination of FrontEndUsers and CustomContent to be able to provide content that is restricted to certain logged-in users/groups.
As for the menu management, there are several ways to accomplish this. The latest Menu Manager release(s?) include the ability to explicitly include or exclude menu items based on the page alias prefix.
This is not the correct syntax, but here is something like what you would want:
(in the above example, group1 would see only menu items specific to their group, and only content specific to their group. Ditto for group2. Group3 would see both sets of menu items, and a content area that is specifically for them.
You need the combination of FrontEndUsers and CustomContent to be able to provide content that is restricted to certain logged-in users/groups.
As for the menu management, there are several ways to accomplish this. The latest Menu Manager release(s?) include the ability to explicitly include or exclude menu items based on the page alias prefix.
This is not the correct syntax, but here is something like what you would want:
(in the above example, group1 would see only menu items specific to their group, and only content specific to their group. Ditto for group2. Group3 would see both sets of menu items, and a content area that is specifically for them.
