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.

CommentFileSizeAuthor
new_nat_features.patch16.04 KBjpsalter

Comments

jpsalter’s picture

jpsalter commented
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.

anantagati’s picture

anantagati commented

Subscribing.

loze’s picture

loze commented

Is anyone planning on adding this to an official release?

Zen’s picture

Zen commented
Status: Needs review » Needs work

I'd like to review this as separate patches.

jpsalter’s picture

jpsalter commented

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?

Zen’s picture

Zen commented

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

ccshannon’s picture

ccshannon commented

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.

ccshannon’s picture

ccshannon commented

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.

derjochenmeyer’s picture

derjochenmeyer commented

Does the patch still apply to current HEAD?

giorgio79’s picture

giorgio79 commented

How about deleting term on node delete? :)

anantagati’s picture

anantagati commented
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.

Status: Fixed » Closed (fixed)

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