Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By rocketboy37 on
I'm not sure if this question has been asked before or not it seems like a common concept. I need to be able to have Departmental Front pages for my intranet site. In other words when staff create a page they need to be able to have the option to post to front page of their Department and not of the entire site.
I looked the "front page" module but that only allows me to change the front page of my entire site.
I understand how to edit and make new forms and create views. My question is how do I make a page the departments default page? So that I can make that an option on my drop-down.
My only option it seems so far is to custom program a new field type but then again where do i point to the default department page in my code?
My issues are the following:
1. Create a default department page.
2. Create a new content type with an option to post to a department page.
3. Only allow user within a department to post to their department page.
Read the following books:
-Building Powerful Website with Drupal 6
-Using Drupal
-Creating Custom Drupal themes
Other Resources
-CCK Docs
-Learn by the Drop
-CCK Module basics
-
My Environment is:
SuseLinux
Drupal 6.13
pathauto
views
cck
Thanks
Comments
Here's a simple way to go
Here's a simple way to go about this, possibly with no programming needed. Create a taxonomy vocabulary called "Departments" or something like that, and create one term for each department. Make selecting a term optional, and assign the vocabulary to whatever node type you want people to use to post "front page" content. When your users want to post content to their department's "front page," have them select the proper department from the taxonomy menu on the node editing page.
Then, the taxonomy term pages for each term simply become the front pages for their respective departments. You could use the Path module to create path aliases for the taxonomy term pages, if the default paths are too unwieldy.
Then have each user bookmark the taxonomy term page for their department, or possibly slap together a module which shows the user a different front page depending on which "department" (role, possibly) they belong to.
Does it need to be more complex than that?
I haven't explained to the
I haven't explained to the users how to use taxonomy yet and they are beginners, if at best when it comes to doing web stuff. They are very old school the intranet itself is a deal right now for them just showing them how to post has been a challenge, which is why I prefer to use things that are familiar.
I would much prefer to have a drop down on the story content type and then they can select from their the front page of the Department they want to post to. Its simple and they can get to it quickly and understand it.
They won't have to know
They won't have to know anything about taxonomy or other info about how things are working on the back end. If you create the taxonomy vocab and make it so only one term from it can be selected, it will appear as a drop-down menu on the node editing page. (Keep the "Tags" and "Multiple select" check boxes unchecked when creating the taxonomy vocabulary.) It sounds like what you're looking for - give it a try.
Off the top of my head I
Off the top of my head I would be thinking organic groups. That said, haven't played with them so not 100% sure they would fit your requirements.
Groups
I believe organic groups would be the way to go. for
1. Create a default department page.
Depending on what you want to do with this "page", organic groups could satisify this need. If a "page" is simply a description of the department then you can create a content type and make it a group. Part of that content type is the body. That body will display when you view the group home page. You can create a template for the group home page too if you want to add other information.
2. Create a new content type with an option to post to a department page.
With groups you can designate any content type as able to be posted into a group. So you can set the "story" and "discussion" content types as group-postable.
3. Only allow user within a department to post to their department page.
Groups handles this as well. Only members of the group (and site admins) can post to that group.
Aside from OG is there any
Aside from OG is there any other way to do this views and cck, I'm finding that OG takes quite a lot to setup initially.
CCK and Views alone won't
CCK and Views alone won't handle the access control you're looking for so there will be some setup involved.