Curiosity (and recognizing I&#39;m about to run into the same problem Nancy had) made me look. Each of the menu item editing forms has an [&#39;#item&#39;] element that gets the original menu item. So instead of a more sophisticated test in _menu_navigation_links_rebuild(), maybe a more sophisticated test assigning a value to $item[&#39;customized&#39;] just prior to calling menu_link_save() (though there&#39;s 17 occurrences of menu_link_save() in core...)?<br>
<br><div class="gmail_quote">On Mon, Apr 27, 2009 at 12:36 PM, Earl Miles <span dir="ltr">&lt;<a href="mailto:merlin@logrus.com">merlin@logrus.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Chris Johnson wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have to agree with Nancy.  Re-weighting a menu item does not qualify<br>
as customized, IMO.  Otherwise, I agree it works as designed.<br>
</blockquote>
<br></div>
The thing is, the system can only tell that there&#39;s an entry in the table, not what part of the item has been modified. I ran into this in some completely unrelated piece of code, where I ended up storing weights separately so that moving an item up or down didn&#39;t constitute modifying it, and it is a lot of extra code just to do that.<br>

</blockquote></div><br>