This patch makes NAT more friendly to custom modules connecting to it via the Drupal node_save() API. This patch adds no extra features, just a slight change on how the 'insert' hook_nodeapi() is handled.

With this patch the following things are possible:

  • Ability to use node_save() to create a node and connect it to an existing term in a NAT-enabled vocabulary (ie: perform a reverse-sync operation)
  • Ability to create nodes in a NAT-enabled content type without having NAT terms created automatically. This is handy if a custom module needs fine grained control over how NAT relationships are created.
CommentFileSizeAuthor
nat.module.api-able.patch792 bytesJames Andres

Comments

James Andres’s picture

James Andres commented

Anyone have feedback? A review / test would be much appreciated :-)

Thanks,

James.

anantagati’s picture

anantagati commented
Status: Needs review » Closed (won't fix)

Second use case you provide directly breaks expected function of NAT module.

Seems like if you want to make such changes in functionality is better to make it completely out of NAT module, so you can use custom module for it. As new maintainer of NAT module, I don't want to support things which support breaking module's native functionality.