I didn't plan to have any user when I designed my new site. At this late, I changed my mind, and facing a few problems. Instead of me creating my musicians profile, I now want each musicians can login and create/edit their own profile to be listed under band member. Problem 1 The taxonomy list is shown on their Content Type but I need to have it selected Band Member by default and I don't want them to have any access to this. How can I control access per field? Problem 2 One of the member made a bad profile. I unpublished it, and created a temporary profile to be posted until she comes back in country to fix it. The problem is that Node Ref from our show schedule and discography lists both, my temporary one and her original. It's just inconvenient, and hoping to make her original not to show up in Node Ref list. Possible? P.S. By the way, my Video module problem was finally solved, after days of trial and error, by switching my OSX locale from Japanese to English :-( -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com>
On Jun 4, 2007, at 8:33 PM, A-NO-NE Music wrote:
Problem 1 The taxonomy list is shown on their Content Type but I need to have it selected Band Member by default and I don't want them to have any access to this. How can I control access per field?
Taxonomy default module can do this, I believe. Laura
Laura Scott / 2007/06/05 / 07:52 AM wrote:
Taxonomy default module can do this, I believe.
Thanks for your help. I searched with this but didn't get too far. Is this an independent module? -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com>
Quoting A-NO-NE Music <madflute@anonemusic.com>:
Laura Scott / 2007/06/05 / 07:52 AM wrote:
Taxonomy default module can do this, I believe.
Thanks for your help. I searched with this but didn't get too far. Is this an independent module?
Taxonomy is one of the optional core modules available upon install. Earnie
Earnie Boyd / 2007/06/06 / 08:21 AM wrote:
Taxonomy is one of the optional core modules available upon install.
Yes, I am using it a lot. What I have been looking for is the access control per user "Create Content". TAC disables Taxonomy all together, and tac_lite seems to work only on viewing, not on creating. Ironically, I am thinking of deleting categories on the content type which allows user to create. -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com>
I might be missing something obvious, but have you looked at using roles to assign the rights to create different types of content -- these rights are assigned to different roles via the node module. This does not extend to users, although if you had an extreme case you could use a blend of roles, cck for creating content types, Organic Groups to create specific groups, and OG Content Type Admin to limit specific content types to specific groups. However, if I understand you correctly, roles should do it. Cheers, Bill A-NO-NE Music wrote:
Earnie Boyd / 2007/06/06 / 08:21 AM wrote:
Taxonomy is one of the optional core modules available upon install.
Yes, I am using it a lot. What I have been looking for is the access control per user "Create Content". TAC disables Taxonomy all together, and tac_lite seems to work only on viewing, not on creating.
Ironically, I am thinking of deleting categories on the content type which allows user to create.
-- Bill Fitzgerald http://www.funnymonkey.com Tools for Teachers 503.897.7160
Bill Fitzgerald / 2007/06/06 / 09:01 AM wrote:
I might be missing something obvious, but have you looked at using roles to assign the rights to create different types of content
Yes, that is what I am doing. To recap my problem, when the user creates a content, I wanted one and only category assigned to that content by default. Right now, the list of the category is visible to the user so I have no control over it. -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com>
I think Laura refers to 'Taxonomy Defaults' module at: http://drupal.org/project/taxonomy_defaults Looks like it's exactly what you need. On 6/6/07, A-NO-NE Music <madflute@anonemusic.com> wrote:
Bill Fitzgerald / 2007/06/06 / 09:01 AM wrote:
I might be missing something obvious, but have you looked at using roles to assign the rights to create different types of content
Yes, that is what I am doing. To recap my problem, when the user creates a content, I wanted one and only category assigned to that content by default. Right now, the list of the category is visible to the user so I have no control over it.
--
- Hiro
Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com>
-- [ Drupal support list | http://lists.drupal.org/ ]
Jim Li / 2007/06/06 / 11:47 AM wrote:
I think Laura refers to 'Taxonomy Defaults' module at: http://drupal.org/project/taxonomy_defaults
Looks like it's exactly what you need.
Took me awhile to understand how this works. You have to remove Category from the content type in order to use this module. Now I see it works as advertised, except that me, the admin also looses access to this, which isn't going to work for me because the entire purpose of this is to prevent them to select but I edit accordingly. -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com>
participants (5)
-
A-NO-NE Music -
Bill Fitzgerald -
Earnie Boyd -
Jim Li -
Laura Scott