Jump to:
| Project: | Content Construction Kit (CCK) |
| Version: | 6.x-2.0 |
| Component: | General |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi,
Sorry if this is inappropriately placed, its my first post.
I am working on a site to allow researchers to create content to describe and make public the material they are working on. Some of the main features of the site are views of content that are associated with particular users, embedded in several areas across the site. This is currently achieved through each user having a "personal tag", their full name, which they can use to tag all the material on the site that they have contributed to and would like to be displayed with their name associated with it.
I have had feed back from my users suggesting that it would be quite tedious to have to manually tag every item they contribute to the site with their name. I am therefore looking for a way to have each user select a "personal tag" when signing up, and then for every item of content they add to the site to be automatically and by default tagged with their tag. The approach I'm currently taking is to use the profile module to create a "personal tag" field that is required on sign up. I then thought I could use the CCK Taxonomy module to create a CCK taxonomy field for all content types, then set the field to a default value of some php that will return the "personal tag" value for the currently logged in user yo create the tag. Unfortunately I have little experience with php and the CCK Taxonomy module and so I'm having trouble implementing my idea.
If anybody has an alternate suggestion or could perhaps help me with my idea, it would be greatly appreciated.
Comments
#1
Maybe you could use a user reference field. You can use PHP code to assign default values to any field, and here you can code almost anything.
Other than that, please try the development forums. I'm afraid this request will be falling down the issues queue with no response.
#2
Automatically closed -- issue fixed for 2 weeks with no activity.