NAT terms not synced when editing taxonomy hierarchy at '/admin/content/taxonomy/[vocab id]'

+1
Yes, I have seen this too. And I have reconfirmed for version 6.x-1.2.

You should not edit the hierarchy at /admin/content/taxonomy/[vocab id]... editing the order/weight is ok and does not cause problems, but changing the hierarchy messes NAT up.

So, a feature should be added to NAT to either
1.) re-sync NAT when the hierarchy is edited at /admin/content/taxonomy/[vocab id]
OR
2.) NAT should prevent the hierarchy from being edited at /admin/content/taxonomy/[vocab id]

I would prefer option #1

I am guessing NAT needs to implement a hook_taxonomy function to sync when taxonomy hierarchy is modified.

Seems like useful / expected functionality. If somebody can make patch it will be wonderful. Otherwise I will look on it next week.

Fixed in NAT-ng module. If you wish you can port patch for NAT module.

anantagati:
So what exactly IS the NAT-ng module?
What is it's purpose?

Looks to me like just a fork of NAT... if so, why not keep going with NAT? Perhaps create a 2.0 version?

arlinsandbulte: Yes, it is fork of NAT module.

I plan to use NAT (NAT-ng) module on very important projects and cannot afford to use unmaintained module.

Before I was co-maintainer (Views Integration) and because module was not getting enough care, applied for to be maintainer #716854: Offering to maintain Node Auto Term [NAT], but shortly seems original maintainer wants to continue.
So after bad experiences, I decided better will be to make fork and be able to improve NAT module. Of course I could maintained module out of drupal.org, but like this many people can get advantage and choose module which will work better for them and will be better supported.

So these are my reasons. You don't need to use NAT-ng, but of course you are welcome if you want to use it and/or provide patches or ideas to improve.

Reverse synchronization is not a feature, yet.