By jrc21 on

I've been reading the documentation for hours trying to figure this out... I have 2 roles set up on my site (other than the defaults), one will be for "officers" of an association, and one for "employers" (it's a job board I'm working on). I want it where when the officers are logged in, they get one custom menu, and the employers another, and those logged in noting. I've found how to do this for specific users (through #s), by name, but not apply a setting to an entire role? Any help? Basically the argument would be if user is officer--> show this code. If employer-->show this other code. If nobody--> show another code.

I don't know much php so you might have to type real slow =).

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

menus, which can be enabled in administer -> blocks can be edited to use role visibility
content types can be shown per role , administer -> permissions (this can be expaned on by investigating modules in the user athentication category of downloads)

views.module can create lists that are also shown on per role basis.

My best suggestion is to set up a test site and work with some of the modules above.

I'd also reconsider using Drupal 5.x. It won't be supported when Drupal 7.x is released and that isn't all that far away relatively speaking. Building on Drupal 6.x ensures you are supported until Drupal 8.x is released.

jrc21’s picture

jrc21 commented

I'm using drupal 5 because there are job board modules for it and that will make that part easier. There are none for drupal 6 that I found. I will try your suggestion of using the menus through the administration section, but I was more looking for a way to code it into the page. But if it works that way, it'll be fine.

Thanks. I'll post again if I can't get it.

vm’s picture

vm commented

likely because you don't need a specific module in D6 to do a job board. A CCK content type and a view provded by the views.module would do this.

Modules that have yet to be moved to D6, are likey to be dead on the vine as they were unneeded for Drupal 6 or they've been replaced with other modules for D6 like jobtrack and jobposting

I'd certainly investigate the use of D6 to complete any projects at this point. D7 is looking like a 1st or 2nd quater 2010 release. Building on D5, because of a contrib module that may or may not make a task easier isn't a prudent move if in 6 - 8 months you've built an unsupported site and modules still won't be updated. At that point you've built deadwood.