I use this module http://drupal.org/project/user_force_term.
Roles: Kommune editor
Vocabulary Name:
Kommuner
Type: Copenhagen
Terms:
Københavns kommune
Odense kommune
Roskilde kommune
Forced term association: (They are only fakeaddresses used for testing)
Københavns kommune Username: Københavns kommune - E-mail address: koebenhavnskommune@tinemuller.dk
Odense kommune Username: Odense kommune Password: Odense kommune E-mail address: odensekommune@tinemuller.dk
Roskilde kommune Username: Roskilde kommune Password: Roskilde kommune E-mail address: roskildekommune@tinemuller.dk
It's functioning great when making nodes/toilets logging in as the users mentioned above. They can ONLY update, delete and so for the Terms they are assosiated with but now come my problem
I have tried registering some more people and on register site I choose - Roles: Kommune editor - Forced term association: And here I choose one of the 3 mentioned above. But the problem is now they can ONLY update, edit their OWN toilest and not ALL the other toilets made by the other people also who have made toilets and that's NOT good.
This was all done because it was so easy with only ONE Content type. Hope you understand my problem and can help and if you don't understand what I'm trying to explain please ask further?
edited 13:51 Sunday: NOT sure this can be done this way. Think I have to use only ONE person and email for each "kommune/City" and then ALL have to use this to log in - but this way I as the admin can't see who has made the info, delete and such things if anything go wrong. :-(
Comments
A couple of options
That is by design unless you use contrib modules.
The Forced Term module only takes care of assigning a specific taxonomy term to content created by a specific user. It doesn't grant other user's with the same forced term setting access to edit affected nodes.
AFAICT you still only need one content type, but you will need a contrib module to let multiple users edit the same node. However: Since the data in your system won't change on a day-to-day basis, and since each municipality would probably have only a couple of people providing said data, it would make sense to just use role-based accountds. I.e. each municipality would get one account, which they could share among the emplyees working on this project. This ensures that reogranizations do not hurt your project since data entry does not rely on user accounts tied to a specific person.
I think you have to consider if you really need to know who created or edited as specific piece of content. Sometimes you have to trust that the users of your site will do the right thing.
If you do want to let multiple users edit shared pieces of content, there are a couple of options (in order of how easy they are to implement):
Thanks a lot for your
Thanks a lot for your explanation so here is how I plan to go which should be OK using your module, right?
Type: Copenhagen
Roles: Kommune editor
Vocabulary Name:
Kommuner
Terms:
Københavns kommune
Odense kommune
Roskilde kommune
toiletdata@tmf.kk.dk which people use to login to CRUD toilets for Copenhagen.
bim@tmf.kk.dk
bam@tmf.kk.dk
busse@tmf.kk.dk
And these persons can also register with their OWN name and info but NOT make toilets but have contact forms and such normal things. But if all 3 login and make changes at the same time?
And then something similar for all the other cities but they still use same Type: Copenhagen
Roles: Kommune editor
edited: 12:43 I have discovered that when I as user1 make new toilet and remember to choose term: Københavns kommune before I save it it's NOT enough - I also have to change Authored by: from admin to Københavns kommune - this had cost me a lot of headache's to change all these notes. But I have also discovered that if I sometime change some info for a toilet used corectly made Københavns kommune for Registerede by: it changes to admin and can't figure out how this can happen?
Hope all my info and mistakes can help someone else. :-)
But if all 3 login and make
I wouldn't worry about that in the first release. You can always figure out a way to fix if it does become a problem later on.
Editing content as user 1: The easiest solution is to not edit other user's content when you're logged in as user 1. An alternative is to use the switch user functionality from the Devel module.