Module development and code questions

I built some categories in the Taxonomy Modul. They can be associated multiply. So I wanted to realize following structure:

ZP
ADAC
*Region 1
*Region 2
DMSB
*ADAC (with child categories)
*BMV

But "ADAC" appears in the wrong way.

The Parents I set for ADAC are and also "DMSB".
But in the Category list (and also in the Site Map of Site Menu Modul) the categories are listed this way:

Hi there,

I'm trying to do a term freetagging insert on node insertion. When somebody creates a node i want to create tags from some node variables. So i have the following code in the hook_insert() function:

I've developed several new modules and node types for a site I'm doing, for one of these node types, after I create a new one with the submit form I want to redirect to another page.

I've been doing this with drupal_goto at the end of the hook_insert and I also tried hook_nodeapi but the issue is that it kicks in before the image attach module has had it's hook_nodeapi called.

now that the debate around version numbers for core has been resolved (it'll be 2-digit version numbers), i'm turning my attention back to the new system for releasing drupal contributions.

there are a couple of main issues in the queue with a series of patches that are getting us close to a working, final implementation:

http://drupal.org/node/83339
http://drupal.org/node/84706

however, the patches are all from before DruaplCon (where there were some good discussions about all this, and some suggestions for changes), and before the switch to 2-digits for core. in writing and thinking about the system over the past few weeks, i've hit a few new complications that i'm unsure how best to resolve. any input on the following would be appreciated...

release nodes that are pointing to the HEAD

in the new system, releases will be real nodes (http://drupal.org/node/83339). if you enable the cvs.module, each release node has a cvs tag/branch that is associated with it (http://drupal.org/node/84706). release nodes that point to a cvs branch (not a tag) get nightly snapshots packaged up, just like the current "releases" we get in contrib. if enabled, cvs.module will form_alter() the release node form to rip out the fields to specify the version #, and add a drop-down to select what cvs tag to use. the only choices would be tags on the project that have no releases associated with them. once the tag is selected, the cvs.module figures out the version # from the tag name. so far, so good...

I'm not sure how this is possible...

I've got a module to create various custom blocks.
When I set the array list to the value of the exploded $delta variable, I can output the value but it always tests as zero.

I've been trying to make a layout following this layoutguide but it wont work. It doesn't bring any changes in the code on the frontpage.

Here'r the code I putted in the node-flexinode-1.tpl file:

<div id="special_content">
<div class="image"><?php print $node->flexinode_1 ?></div>
<?php print $node->flexinode_2 ?>
</div>