By walshb on

How can I set up a user that when they log in are automatically taken to a specific page with limited permissions for changing the content of that page. I have read about access control, rules, and cck. Installed all but do not seem to get the control I need, or perhaps I am lacking the knowledge to execute. I am newer to Drupal. Falling in love. But just like any good relationship around 6 months to a year, I am being tested.

Thanks for the help ahead of time.

⋅ Categories: Drupal 6.x

Comments

WorldFallz’s picture

WorldFallz commented

You should be able to setup a simple redirect upon login with core triggers and actions. Set up the redirect action (admin/settings/actions) then attach it to the user login trigger (admin/build/trigger/user).

For restricting access to nodes, you'll need to use one of the access control modules (ie content_access, simple_access, nodeaccess_userreference, etc). Which one you use will depend on the details of how you want to control access.

walshb’s picture

walshb commented

I am going to give it a shot tonight let you know tomorrow. Thanks for the quick reply.

walshb’s picture

walshb commented

I have set up an action to redirect to the page. I think I connected it to the trigger by selecting the when: Trigger: After a user has logged in Name Operation Redirect to Bulletin

Now how do I redirect only certain users. I suppose this is the ie content_access, simple_access,
nodeaccess_userreference. I had previously installed content_access but do not see the pages I should based on the description.

I am very grateful for the help. I am feeling like a solution is very close. Thank you very much. I am new but eager to learn more.

The site I am working on is for a High School in Philadelphia. With no funds and support this has proven to be a miracle solution.

Thanks again.

WorldFallz’s picture

WorldFallz commented

Core triggers and actions are very basic-- in order to only redirect certain users you'll have to use the rules module.

Access control modules control access to content (ie who can view what nodes)-- it has nothing to do with triggering actions for certain users.

bgilday’s picture

bgilday commented

I recommend that you try the Login Destination module. This module allows you to define the custom page each user is sent to after login. You can redirect every user to a single URL or, in your case, write custom PHP code to implement fine-grained redirect control based on specific characteristics of each user, such as their userid or role.

Regarding acces permissions - you might be able to leverage the Content Profile module to have a specific page automatically created for each user. You can setup a custom content type to act as the user's 'profile' page. Your custom content type could be anything really, it doesn't have to contain a set of profile fields. You could then use normal permission settings to allow users to only edit their own profile node.

(Note, I've used Login Destination before to much success but have not given Content Profile a test ride so I am not sure exactly how it works).

I hope this helps.

Brian Gilday
Municode
www.municode.com

WorldFallz’s picture

WorldFallz commented

Login destination is a great module but it only does one thing-- rules is infinitely flexible. Its does all login destination does and much much much more.

bgilday’s picture

bgilday commented

I agree that Rules/Triggers/Actions are very robust/flexible and could definitely be configured to achieve the end result. Flexibility, however, also brings with it complexity. Login Destination addresses his very specific requirement and he seemed to be having some configuration issues with the other approach. So, I am simply presenting a straight-forward alternative. Either way will work.

Brian Gilday
Municode
www.municode.com

walshb’s picture

walshb commented

I was able to set user roles, nodeaccess, and content access to provide a solution. Once I realized how to restrict editing on certain nodes it became easy. I created a node specific to the job. Set a user only able to write and edit own node created. After this was established the redirecting and limiting access to other pages was no longer a concern. Without both of your suggestions, I would have never figured out how to use these powerful tools. Thank you both very much.