Separate Taxonomy Per User, but Display To All???

i've only used this module for d5 but what we did was modify for instance node.tpl.php to append the private taxonomy terms to the end of category output on the content-type that sports the private taxonomy. this code is for the d5 version so you may need to adapt for d6.

if ($node->type == 'blog_post') {
	$result = db_query('SELECT v.vid, v.tid, name FROM {term_data} v INNER JOIN {term_node} p WHERE v.vid = 13 AND v.tid = p.tid AND p.nid='.$node->nid.'');
	if ($result) {
		$bcategories = array();
		while ($v = db_fetch_object($result)) $bcategories[] = l($v->name, 'blogs/'.$userurl.'/'.strtolower(pathauto_cleanstring($v->name)));
		if ($bcategories) $categories = '| Blog Categories: '.implode(', ', $bcategories);
	}
}

If its a blog_post, get the private terms from vocabulary id 13 the database and alter the $categories array to append our custom output of the private taxonomy in teaser or full node view.

Note you will need to change out the content-type and vocabulary id (v.vid in the example)

Did you, benahlquist or anybody else, get this to working?

I need others to view the tems to but dont know how to ?

Thanks for any answer.

The permission 'view private taxonomies' has been added. This allows users with this permission to view terms belonging to other users but not modify them. This change has been added to 7.x-1.x-dev. I hope to backport it to 6.x-1.x-dev shortly.

Thinking about this, only the user's terms should be displayed in the node add forms. It appears that even without the 'view private taxonomies' permission, all the terms were shown in a term reference attached to a node. So I have added code to remove all terms other than the user's terms when a private vocabulary is attached to a node. Thus, with both permissions a user can administer their own terms, add them to their content, and view all of the terms attached to other users' content.

This has been backported to 6.x-1.x and is in the dev branch. Still more testing before a formal release for 6.x-1.x and 7.x-1.x but the functionality should be there.

This sounds good, i will have to install the module again soon. Thanks a lot.