Nope that was how it goes and the /all feature works perfect. Another thing I'm looking to do is to calculate fields but not sure if this is possible.<br><br>What I'm trying to build is a time tracking application so if I create views based on taxonomy I would like to calculate the total for each "project" or "client" or "task" in the appropriate view. How would I go about this?
<br><br>thanks again.<br><br><div><span class="gmail_quote">On 9/11/07, <b class="gmail_sendername">Cog Rusty</b> <<a href="mailto:cog.rusty@gmail.com">cog.rusty@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 9/12/07, Chris McCreery <<a href="mailto:chris.mccreery@gmail.com">chris.mccreery@gmail.com</a>> wrote:<br>> So for this to work properly I would set the vocabulary like this?<br>><br>> Hierarchy:<br>> Disabled
<br>> Single<br>> Multiple<br>> Allows a tree-like hierarchy between terms of this vocabulary.<br>> Related terms<br>> Allows related terms in this vocabulary.<br>> Free tagging<br>> Content is categorized by typing terms instead of choosing from a list.
<br>> Multiple select<br>><br>><br>> Or do I need something else? I notice when I create a new node I see the<br>> project name listed but not a link to the client to bring up all items<br>> associated with it. Is there a way to do this or do I really need to do it?
<br>><br>> Thanks<br><br><br>Yes, just that, except if I did not understand. correctly. You said<br>you have "a taxonomy as follows"<br><br>Client<br>--Project<br><br>I took that to mean that client and project are both categories, which
<br>have a parent-child relationship, and that you have a pattern of<br>categories with a structure like this<br><br>Client name 1<br>-- Project name 1<br>-- Project name 2<br>-- ...<br>Client name 2<br>-- Project name 3<br>
-- Project name 4<br>-- ...<br><br>and that you wanted to be able to tag nodes with projects and then to<br>be able to list them either by project or by client. If it is so, it<br>can be done without tagging clients but only projects, using
<br>taxonomy/term/client-ID/all<br><br>If I got it wrong and your structure is different, then some more<br>explanation would help.<br><br><br><br>> >On 9/11/07, Cog Rusty <<a href="mailto:cog.rusty@gmail.com">cog.rusty@gmail.com
</a>> wrote:<br>> ><br>> > On 9/12/07, Chris McCreery <<a href="mailto:chris.mccreery@gmail.com">chris.mccreery@gmail.com</a>> wrote:<br>> > > Hi I am trying to create a taxonomy as follows<br>
> > ><br>> > > Client<br>> > > --Project<br>> > ><br>> > > I would like the user to just select the project and have the client<br>> term<br>> > > added to the node as well but can't seem figure which type of vocabulary
<br>> I<br>> > > need. Any help would be great.<br>> ><br>> ><br>> > As far as the node list pages are concerned, tagging the nodes with<br>> > "client" is not necessary.<br>> >
<br>> > /taxonomy/term/[client_id]/all will also list nodes tagged with project.<br>> ><br>> > And generally, clients can be easily derived from projects with some<br>> > code, and vice versa.<br>> > --
<br>> > [ Drupal support list | <a href="http://lists.drupal.org/">http://lists.drupal.org/</a> ]<br>> ><br>><br>><br>><br>> --<br>> Chris McCreery<br>> --<br>> [ Drupal support list | <a href="http://lists.drupal.org/">
http://lists.drupal.org/</a> ]<br>><br>--<br>[ Drupal support list | <a href="http://lists.drupal.org/">http://lists.drupal.org/</a> ]<br></blockquote></div><br><br clear="all"><br>-- <br>Chris McCreery