One of the very consistent things of the Drupal administrative UI is that after creating a setting you can always see and then edit that same setting via the same UI.
This is not the case for menu settings on the new node/xxx/edit form for D7.
Here is how it currently works:
You create content at: node/add/article. You scroll down and see "Menu settings," which is selected by default among those other settings categories (Comments, authoring, etc). "Not in menu" appears below the section title, and there is an unchecked checkbox called "Create menu item" on the right. You click on that box and a fieldset opens below for you to create your menu settings. You can set the "Menu Link Title," the "Parent Item" (only menus enabled at admin/structure/types/manage/article are available for selection), and the weight. (No "description" field is available as you would find via the menu admin interface. The link title attribute will be automatically set to the node title.)
You save the node. You click "edit." The "Menu Settings" are selected by default at the bottom area of the form. Now the "Menu Link Title" you created upon node/add is showing up under the "Menu Settings" heading. However, you do not have access to edit any of those settings you just made. The same "Create menu item" checkbox is there. The moment you check that box, your previous settings are overwritten upon "Save." The form never accesses your previous settings for reference or for easier editing. If you wanted to fix a typo in the Menu title link, you'd have to retype the whole link and reassign the parent item and weight.
In sum... the behavior of the Menu Settings sections of the node/add and node/xxx/edit form are inconsistent with the Drupal UI and with best practices for CMS user interface design. Settings that are created via a form should be able to be retrieved and then changed via the edit version of that same form.
Shai
Content2zero
Comments
Comment #1
sunMarking as duplicate of #322703: Use on/off checkbox to enable node's menu item, which was committed by accident.
Comment #2
Shai commented@sun, if #322703 was already committed... accident or not, don't we need a new place to begin addressing the problem. Why not here?