Download & Extend
Node Auto Term [NAT] » Issues

Four additional features for NAT

Posted by jpsalter on February 5, 2008 at 10:22am
Project:Node Auto Term [NAT]
Version:7.x-1.0-alpha1
Component:Code
Category:feature request
Priority:normal
Assigned:jpsalter
Status:closed (fixed)

Issue Summary

I've patched NAT many times for different clients for different reasons. Recently, I needed all the functions for a single website. So, I've combined the features into HEAD and made a patch.

New features

  • Node deletes: Optionally delete child nodes associated via NAT.
  • Maintain hierarchy on unassociated vocabularies
  • Sync terms -> nodes + Bonus: term depth can determine nodetype
  • i18n language for term: Optionally add i18n language data to term

I've marked this patch as needs work - since my testing has not been exhaustive, the code probably does not adhere to Drupal's standards, and I think I missed some t() functions. And, yes I know patches should break out individual functionalities. But, I also know that I never follow through when I plan to make individual patches *sometime* soon.

AttachmentSize
new_nat_features.patch16.04 KB
Login or register to post comments

Comments

#1

Posted by jpsalter on March 12, 2008 at 4:45pm
Status:needs work» needs review

I've used this patch for a while and it hasn't caused me any errors. I think it is ready for testing.

#2

Posted by anantagati on March 16, 2008 at 5:29am

Subscribing.

#3

Posted by loze on November 13, 2008 at 5:34am

Is anyone planning on adding this to an official release?

#4

Posted by Zen on March 1, 2009 at 6:27am
Status:needs review» needs work

I'd like to review this as separate patches.

#5

Posted by jpsalter on March 1, 2009 at 6:44am

Thanks for the bump. If you're interested in the patches - I'll break them out and update them. Should I work against 5.x-3.1 or 6x.-dev?

#6

Posted by Zen on March 1, 2009 at 6:57am

Against 6 please - Cheers :)

Re: Term -> Node sync - please separate the "bonus" feature into a separate patch as I'm trying to minimise "feature creep" as much as possible.

Thanks a bunch,
-K

#7

Posted by ccshannon on April 14, 2009 at 1:47am

Does "Sync terms -> nodes + Bonus: term depth can determine nodetype" mean that one can assign more than one content type to a single vocabulary, based on the hierarchical level? So , content type A syncs to Vocabulary A top level terms, content type B syncs to Vocabulary A mid level terms, and content type C syncs to bottom level terms?

Thanks for all the great work.

#8

Posted by ccshannon on April 17, 2009 at 7:01pm

Oops, ignore my comment, thanks. Just discovered I can already do exactly that: three-level vocabulary, each level represented by a separate content type using NAT. Works fantastically!

Got it confused with "one node can only create one term" and reversed it thinking "one vocab can only be represented by one node type" but it's working well.

I think you're talking TAN functionality where the term can be used to determine the matching node type by its place in the vocabulary hierarchy, which is also very cool. Cheers and happy hunting.

#9

Posted by derjochenmeyer on June 15, 2009 at 2:20pm

Does the patch still apply to current HEAD?

#10

Posted by giorgio79 on August 5, 2009 at 8:42pm

How about deleting term on node delete? :)

#11

Posted by anantagati on March 6, 2010 at 3:58pm
Version:master» 7.x-1.0-alpha1
Status:needs work» fixed

Closing issue as there is long time no progress. If somebody has interest about those features, please post each feature as separate issue, so it is easy to manage and work on it.

#12

Posted by System Message on March 20, 2010 at 4:00pm
Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.