By sisko on

Hi,

we are putting together a drupal website to front our customer activity records maintainance system.

We've setup two nodes/content types - Activities and EachActivity.

What we're trying to accomplish is a means for staff to create different 'Activities' and allow them to store 'EachActivity' inside a target 'Activities'.

So to recap, we need help attaching a group of 'EachActivity' nodes to an 'Activities' node.

Will you experts lend some wisdom to help us?

ps: anyone is an expert by comparrison to us :~)

⋅ Categories: Drupal 6.x

Comments

jastraat’s picture

jastraat commented

EachActivity could have a nodereference field where when a staff member creates a new node, they select the 'Parent' Activity node for that EachActivity. Then, use views to create a view of all the EachActivity nodes that are related to a given 'Activity' node.

------------------------------
http://fraggles.artsci.wustl.edu (Drupal user documentation and development blog)

sisko’s picture

sisko commented

Thanks for that. That works fine. There is however a slight problem. Only our administrator is meant to see all other staff members 'Activities'.

Currently, like you said we have staff creating their 'Activities' and they add their subsequent 'EachActivity by selecting which 'Activities' from a drop down list.

But as I was saying above, staff members can see each others 'Activities' which we don't want to allow and we can't find a relevant setting to stop this in the user permissions.

Any suggestions ;~)

Thanks in advance.

sisko’s picture

sisko commented

just had another thought. Can anyone advice on if it's possible to use Drupal to setup separate database tables so there is no colliding of diffeent members of staffs' data ?

Please HELP !!!

WorldFallz’s picture

WorldFallz commented

You don't want to go down that road, use one of the access control modules (content_access, nodeaccess, taxonomy_access, simple_access, etc.)

===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz

sisko’s picture

sisko commented

hey guys,

I am still looking for help in resticting our staff from viewing each others data. I took WorldFallz kind advice and installed the only module he suggested that I could find - simple_access.

Having installed it, I ticked off all the available options without success.

Can anyone offer some helpful insight !?

Thanks you guys for all you responses :~)

jastraat’s picture

jastraat commented

If you want to restrict the activities that a staff member sees as options when creating eachactivity, you can create a custom view with a filter "node author is current user" (or equivalent). Then, select that view as the one you want to use for the list in the nodereference field. Each staff member should only see their own content.

------------------------------
http://fraggles.artsci.wustl.edu (Drupal user documentation and development blog)

sisko’s picture

sisko commented

can I impose on you for some detailed instructions on achieving your suggested method?

We are too new at this to even know how to proceed ...

sisko’s picture

sisko commented

is it possible to alter my 2 simple content types to restrict them to author viewing and editting ?

We really need and appreciate your help >>>

sisko’s picture

sisko commented

can anyone tell me how we can allow individual staff member create their own content types and add them to their own defined categories ?

jastraat’s picture

jastraat commented

If you mean giving them administer content type privileges - that is probably a very bad idea. You can give staff members 'edit own' permission without giving them 'edit any' permission for each content type. That would allow them to edit their own content (anything they had created) but not the content of any other staff member.

------------------------------
http://fraggles.artsci.wustl.edu (Drupal user documentation and development blog)