Re-implement with hook_link_alter()

David,

i like it very much. As soon i get some time, i will submit such feature. thanks.

Can you create a patch?

regards,

massa

I've found the simplest method is to use hook_link_alter, since you don't have to worry about deleting variables in hook_preprocess_node() that some other module might be relying on.

This example re-uses some of the code from _taxonomy_hide_nodeapi. Sorting will take a little more work thought,

<?php
/**
 * Implementation of HOOK_link_alter
 * 
 * removes links to taxonomies we are hiding
 * 
 */
function taxonomy_hide_link_alter(&$links, $node) { 
  
  // This module only cares with nodes that have taxonomy terms
  // assigned to them.  
  if (!empty($node->taxonomy)) {
    
    // Get all hidden vocabularies; keys of $hidden are the vocabulary ids.
    // Apply either the node type filter or the global filter, not both
    // First, apply filter for current node type, if it exists, else apply global filter
    // In this way, the setting for the node type overrides the global setting
    // If a filter for this type is not set, the global filter will be used.
    if ($hidden = array_filter(variable_get('taxonomy_hide_vocabularies_'. $node->type, array())) or
        $hidden = array_filter(variable_get('taxonomy_hide_vocabularies', array()))) {

      // Hide terms by removing them from the link array
      foreach ($links AS $module => $link) {
        if(sscanf($module, 'taxonomy_term_%d', $tid)) {
          if($hidden[$node->taxonomy[$tid]->vid]) {
            // Remove all taxonomy links
            unset($links[$module]);
          }
        }
      }
    }
  }       
}
?>

Adam,

nice! i will take a better look soon.

regards,

massa

Subscribing.

I have a site I'm working where I'm using one vocabulary to organize content into the sections it belongs to, and a separate vocabulary to provide author-entered content tags. The second vocabulary is what I'd like to show, and the first vocabulary I'd like to hide, but still have access to in the node object so I can use it's values elsewhere.

Cheers!

Agreed, this is a troublesome issue (just spent 20 man-hours between 5 people trying to find the issue, then found it was taxonomy_hide). Taxonomy_hide worked for hiding taxonomies on view, but when Acquia Search re-indexed, most of our taxonomies were suddenly hidden.

So, a way to non-invasively hide the taxonomy ID's would be ideal. Since taxonomy_hide does more than hide, would it be possible to list this on the frontpage of the module download to try to save other people from a 20 man-hour hunt? I imagine this module can be very useful, but in complex configurations, it can really cause some issues.

Perhaps internally we can get around to coding a patch that will work, since it seems like we'll need this functionality.

Thanks all for your contributions to this project! You guys rock!

subscribe...