I'm a bit curious about the way you were able to do this using hook_taxonomy() since that hook is always called after the fact, meaning any "locked" operation has already been committed to the DB once your code is called. Whatever the implementation, though, I do not think this belongs in core: extra access control modules like this one (cck field perms or profile perms, for instance) are in contrib already. ________________________________________ De : development-bounces@drupal.org [development-bounces@drupal.org] de la part de Pierre Rineau [pierre.rineau@makina-corpus.com] Date d'envoi : jeudi 6 août 2009 10:14 À : development@drupal.org Objet : [development] New module Hi, I'm doing a simple module that allow taxonomy term locking. By locking understand that it allow only users with a new permission to move or edit them, but all other terms remains still editable by anyone with the 'administer taxonomy' permission. It uses the hook_taxonomy() and alter the main taxonomy term list overview to handle locked positions for some terms. The goal of this module is to intensively use taxonomy_menu, but with finer permissions, and locked subtrees. I looked up a bit on modules that exists, I did not found such module, the fact is we are going to use it for many projects. Does anyone is interested in me commiting it on drupal.org? Pierre.