Hi, I fear I am a bit lost here, I want to have the site look very clean from a public standpoint with a few public pages and a login. Once a student or teacher logs in then I want them to have access
One teacher providing all information to the different classes. This is a very simple
version since the roles are easy to distribute: there's one "moderator" namely the
teacher and all other users have the "student" role in succession to their class
role. Using taxonomy_access each piece of content will have it's own tag/class that
only those students can see, next to a "protected" tag so that any student can see
the content and a "public" tag for anyone (not logged in) to see. A group can be
created per class, as well as a "student group" for the pupils to gather and discuss.
A forum should probably be set up with some default categories.
Ok, this looks like it will fit the bill, but for the life of me I am confused. I don't need some of these features yet, but will want them, so how about turning them all off and bring them up as I need them so there is less clutter on the screen too.
Can anyone help a newbie walk for a little bit. I would appreciate it. I can scrap and re-start the install if necessary since my mucking around may have mest things up.
Thank you.
Comments
Comment #1
bonobo commentedFirst, sorry to be so slow in responding to this -- I didn't see it when it first was posted --
WRT
I would strongly recommend against using taxonomy access control for this. Use the built in Organic Groups, and create group-specific vocabularies.
WRT turning the features off: the easiest way would be to edit the taxonomies and remove the vocabularies from the various content types. This way, people creating content would not see the taxonomy options. To further clean up the screen, you could limit block visibility by role in the block administration pages.