Taxonomy

This is how one would embed it in a node.tpl.php, but this should all be done in a pre-process function instead.

Struggling with taxonomy import.

After stripping everything out, the conclusion is that taxonomy_save_term, by itself, without even the hooks to add extra data, is simply too slow, with a minimum of three database calls per term. (data, hierarchy, vocabulary)

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 1048576 bytes) in /RCS/agaric/agaric-sites/scf/includes/bootstrap.inc on line 836

134,217,728

Increased to 256MB. It ran forever, then returned this:

<?php
// commented out below from TCS, possibly of interest
  //  $term = (object) array(
  //    'predicates' => array(),
  //  );
   
//    $term->id = $concept->getAttribute('id');

//    $term->uri = $url;

//      $term->name = $termname->textContent;
//      $term->namerefs[] = $termname->getAttribute('ref');

The parser needs to follow the instructions here:
http://geneontology.org/GO.format.obo-1_2.shtml

To import a file of the kind available here:
http://geneontology.org/GO.downloads.ontology.shtml

How to in Views 2

Using a taxonomy term associated with a node as the argument in your block view. In the original Views module, the PHP Argument handling code was a collapsed fieldset that opened to reveal a textarea in which to input code. In Views 2 this is still necessary, unless we're missing out on some uber-advanced method, but harder to get to.

"chx has a dropbox module in CVS, which'd provide a 'clipboard' for putting stuff into, for operations to be taken on later." (catch comment on Taxonomy improvements thread)

Resolution

This question came from a fellow couchsurfer.

We are dedicating our selfs almost all summer to learn drupal and make a website for artists.

The Question: How to use arguments to make a block view show content associated with pages

ok

so there are industry pages under the industry dropdown. AND there are products pages under the products dropdown, products is its own content type, industry pages are pages, the products content type has a vocabulary associated with it that basically has all the industries in it.

Current text and project: http://www.drupal.org/project/edit_term

Edit term provides a block on taxonomy listing pages with links to edit taxonomy terms .

UPDATE: With a patch from new co-maintainer Dan Morrison (dman), edit_term will become 75% more Drupaly as it provides edit and view tabs directly on taxonomy listing pages.

On the last hours of the coding sprint following the amazing Drupal conference, I accosted Steven Peck and asked in person about (one of my many) pet issues: that documentation (or any non-spam node) not be deleted from Drupal.org. Assorted drupallers wandering around MIT agreed with this in principal, but also agreed with Steven that old content referring to unsupported versions of Drupal would have to be very clearly flagged.