Term Reference Hierarchy [#1204512]

Since there's no obvious way of saving term hierarchy when creating a node, this module was created.
The user creates 2 term reference fields, referencing the same taxonomy vocabulary.
Then, using this module you can set which field is the "parent" term and which one is the "child" term field. When saving the node, taxonomy terms are created and their hierarchy is saved.

Instructions on how to use:
a UI is not yet available but it's very easy to customize.

line 8 of term_reference_hierarchy.module
replace 'content' with your content type machine name.

line 9 of term_reference_hierarchy.module
replace field_tag_lvl_1 with the machine name of the field you want to declare as you "parent" term.

line 10 of term_reference_hierarchy.module
replace field_tag_lvl_2 with the machine name of the field you want to declare as you "child" term.

TODO: a UI that will allow selecting the parent and child terms as well as the content type.

link to sandbox: http://drupal.org/sandbox/aristeides/1202856

Comments

Comment #1

ccardea commented 4 July 2011 at 19:17

The waiting time for a project application review is currently approaching six weeks. Please consider shortening your wait time by contributing to the code review process. All it takes is basic module writing skills, plus it is a great way to add to your knowledge of Drupal. Please visit http://groups.drupal.org/code-review for details on how to participate.

Comment #2

jpontani commented 29 August 2011 at 18:06

Status:

Needs review

» Needs work

Quick review:
- README should be README.txt
- remove drupalkey and drupalkey.pub from your repo
- Add a line break after your version line in .info file
- Indentation should be done using 2 spaces per level, not tabs
- Remove your commented drupal_set_message lines
- Doxygen comment should be "Implements hook_node_presave()." Then if you need, add extra comment lines after if you need to describe in detail what exactly it does. You don't need the @param directive as that's documented on hook_node_presave.
- Replace 'und' with LANGUAGE_NONE (http://api.drupal.org/api/drupal/includes--bootstrap.inc/constant/LANGUA...)

Having an end user have to modify PHP code to get it working is not exactly what you want to start out with, as it's very easy to mess stuff up and WSOD a site, even with just a single missing semicolon.

Start with just the UI for customizing which fields are parent/child without having them be hardcoded.

Comment #3

misc commented 21 January 2012 at 21:35

The applicant has been contacted to ask if the application is abandoned.

Comment #4

aristeides commented 22 January 2012 at 20:42

This application for full project access is postponed because at the moment I don't have the time to deal with it.
However I wouldn't say it's "abandoned", the project that has been taking up most of my time will be finished in 1-2 months so at that point I'll get back to finishing this module.