Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
menu system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
27 Apr 2009 at 21:46 UTC
Updated:
20 Sep 2017 at 19:02 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
nancydruBTW, this patch can be back ported to 6.x as-is. However, the damage to menu_links has already been done although an individual admin can easily undo it with "UPDATE `menu_links` SET customized = 0" (assuming there is no "real" customization in there).
Comment #2
Anonymous (not verified) commentedWell the patch needs a review.
Comment #3
chx commentedNancy, thanks for the patch. I think it's going in a good direction but comments go above the code line not besides. You are using some strange quotes, just use plain apostrophe. Also please check menu_edit_item too. You can change weight there too.
Comment #4
chx commentedSorry, I have crossposted but this is indeed not developer experience. More like user experience.
Comment #5
nancydruComment #7
nancydruI have no idea why it should fail; the patch was created by CVS from a HEAD checkout.
Comment #8
nancydruComment #10
nancydruAre the tests, by any chance, flawed in this respect?
Comment #11
deviantintegral commentedIt strikes me that modules/menu/menu.api.php should also be updated to contain documentation as to what constitutes a customized menu entry. The current docs make it seem like there are no restrictions, which I think caused much of the confusion in the first place.
Comment #12
nancydruIt should also mention the ramifications of being "customized" - and that pretty much means that hook_menu_alter can no longer be relied on to make menu changes.
Comment #13
Anonymous (not verified) commentedThe tests didn't fail because it couldn't apply the patch, it failed during the 400+ tests it does for creating and deleting menu items.
Most of the API documentation resides in the body of the code. The API documentation that doesn't reside within the body of the code resides in one of the folders of http://cvs.drupal.org/viewvc.py/drupal/contributions/docs/developer/ so the proper way to change the documentation is to submit a patch.
Comment #14
Anonymous (not verified) commentedAnd you may need to modify the tests to fit the new functioning of the API.
Comment #15
nancydruI have not gotten to where the tests make sense to me yet, so I can't do much about that.
Comment #16
themselves commentedErm... Why doesn't hook_menu_alter change a customized menu item? That makes no sense at all. Drupal seems to be going out of its way to make life difficult for people who'd like to have dynamic menu titles. Surely it is quite reasonable to create a menu item with hook_menu and then want to change it later on with hook_menu_alter? Dynamic titles in hook_menu don't work (until you clear the cache), hook_menu_alter doesn't work if you've had the audacity to want to order your menu items... What happened to good ol' $may_cache from D5? That worked perfectly for this sort of situation!
Comment #17
nancydruThanks for reminding me about this one. Now that I understand a bit about the testing now, maybe I can make this pass.
Comment #18
chx commentedWhat happened to this?
Comment #19
nancydruRealLife™ seems to have gotten in the way.
Comment #20
gagarine commentedUsability is preferred over UX, D7UX, etc. See https://www.drupal.org/issue-tags/topic
Comment #21
nancydru