Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
No menu on the fly. No custom menus. But the overview, the edit, the enable/disable, the delete/reset works. That's a beginning.
Comment | File | Size | Author |
---|---|---|---|
#32 | menu_99.patch | 53.72 KB | chx |
#31 | menu_98.patch | 49.78 KB | chx |
#28 | menu_97.patch | 50.17 KB | chx |
#24 | menu_95.patch | 50.14 KB | chx |
#16 | menu_94.patch | 49.95 KB | chx |
Comments
Comment #1
chx CreditAttribution: chx commentedTo test, apply patch and try to add/edit (does changing parent work? what about the weight?)/delete and enable/disable/reset menu items.
Comment #2
blakehall CreditAttribution: blakehall commentedDoesn't apply to an updated CVS checkout of HEAD.
patching file includes/menu.inc
Hunk #2 FAILED at 559.
Hunk #3 succeeded at 630 (offset -3 lines).
Hunk #4 FAILED at 638.
Hunk #5 succeeded at 662 (offset 1 line).
Hunk #6 succeeded at 674 (offset -1 lines).
Hunk #7 succeeded at 726 (offset 1 line).
Hunk #9 succeeded at 927 (offset 2 lines).
2 out of 9 hunks FAILED -- saving rejects to file includes/menu.inc.rej
patching file modules/menu/menu.module
Hunk #2 FAILED at 121.
1 out of 9 hunks FAILED -- saving rejects to file modules/menu/menu.module.rej
patching file modules/node/node.module
Hunk #1 succeeded at 1136 (offset 5 lines).
Hunk #3 succeeded at 2117 (offset 11 lines).
patching file modules/system/system.module
Hunk #1 succeeded at 378 (offset 5 lines).
Hunk #2 FAILED at 2170.
1 out of 2 hunks FAILED -- saving rejects to file modules/system/system.module.rej
patching file modules/user/user.module
Hunk #1 FAILED at 480.
Hunk #2 succeeded at 1868 (offset -4 lines).
Hunk #4 FAILED at 1894.
2 out of 4 hunks FAILED -- saving rejects to file modules/user/user.module.rej
Comment #3
chx CreditAttribution: chx commentedReroll.
Comment #4
blakehall CreditAttribution: blakehall commentedAfter some trouble shooting in IRC:
Disabling / Enabling and Resetting do work as expected.
Comment #5
chx CreditAttribution: chx commentedFixes.
Comment #6
chx CreditAttribution: chx commentedComment #7
add1sun CreditAttribution: add1sun commentedDid some quick testing (need to get to work) but here is what I found:
New menu gets added to the DB but does not appear on admin/build/menu.
Editing a menu item worked (title, weight and description) but then it changed Parent Item to Root (whether this was edited or not) and cannot be changed back.
Resetting does nothing. Click the reset button and you are returned to the same page. The menu item still appears in the menu.
Expansion does not work.
On the other hand weighting is working. :)
Comment #8
dmitrig01 CreditAttribution: dmitrig01 commentedWith parents: If I create an item titled Blog entry (blog module not enabled), and I set the parent to Create Content, then it appears under root. If I then set it to have the parent Themes, then it appears under Site Building. So changing parents works, but the items don't appear in the right places. Plus, if I set it to have a parent of My Account, then I get the following error:
notice: Undefined index: user/% in /*****/includes/menu.inc on line 637.
If I disable page and story module in the menu, is it intended behavior for them to still show up on node/add?
Comment #9
dmitrig01 CreditAttribution: dmitrig01 commentedReset works as expected.
But one problem I had was if I set admin/content/node to weight 10, it wouldn't stay under admin/content, it would go down to admin. I think this is because the pids are one level too high.
Comment #10
pwolanin CreditAttribution: pwolanin commentedsubscribing... I also want to figure out how the new menu API can fit in with: http://drupal.org/node/128731
Comment #11
chx CreditAttribution: chx commentedSeems we were close. Actually, everything worked for me but reparenting.
Comment #12
chx CreditAttribution: chx commentedLeft out menu.install , sry.
Comment #13
chx CreditAttribution: chx commentedNow, a lot of mysteries are solved -- you can't just add any foo path, it won't work and now there is a validate to enforce valid paths.
Comment #14
chx CreditAttribution: chx commentedThe validate needs to skip external URLs (thanks webernet)
Comment #15
chx CreditAttribution: chx commentedAgainst HEAD.
Comment #16
chx CreditAttribution: chx commentedWith install and without parse error.
Comment #17
blakehall CreditAttribution: blakehall commentedinternal paths work
external paths are a TODO (per chx in irc)
updates/adds/deletions/resets etc work
Comment #18
chx CreditAttribution: chx commentedYes. I need to think on how external URLs effect everything -- the build, the translate. I do not have the time for them now.
Comment #19
Dries CreditAttribution: Dries commentedHow is menu_edit.admin being used, and why?
Comment #20
pwolanin CreditAttribution: pwolanin commentedA node added as a menu item cannot be viewed. To reproduce:
same bug with clean, non-clean URL setting. note- PHP 4.4.4, MySQL 4.1.22
Comment #21
pwolanin CreditAttribution: pwolanin commentedbug #2:
created a second node- tried to add as a child menu item under "My Account".
get error message:
notice: Undefined index: user/% in /Users/Shared/www/drupal6/includes/menu.inc on line 637.
Comment #22
pwolanin CreditAttribution: pwolanin commentedbug #3:
Edit a newly created menu item pointing to a node. Try to move it to a different place in the menu hierarchy. Form validation error message:
There is already a menu item pointing to this path.
This error may be specific to node menu items. Trying to move a module-defined menu item works, but gives the same notice as above:
notice: Undefined index: user/% in /Users/Shared/www/drupal6/includes/menu.inc on line 637.
Comment #23
pwolanin CreditAttribution: pwolanin commentedin the list of steps in #20, I should have noted that the menu.module was enabled immediately *after* applying the patch.
Comment #24
chx CreditAttribution: chx commentedNode viewing is noted already in another issue http://drupal.org/node/132225 . It's requires quite some work.
The other two I fixed, thanks.
Comment #25
pwolanin CreditAttribution: pwolanin commented@chx- in the context of hierarchical page structuring, the menu module will, I guess, be an example of how another module can maintain custom menu hierarchies? Or will the menu module have an API for this?
Comment #26
chx CreditAttribution: chx commented@pwolanin, let's discuss somewhere out of this issue , IRC , IM whatever works for you.
Comment #27
Dries CreditAttribution: Dries commentedI tried the patch and got this:
Comment #28
chx CreditAttribution: chx commentedI forgot the utf8 comment from the table definiton. The rows notice is also fixed --but that only fired if you had no items at all which is quite impossible because you are able to see admin/build/menu .
Comment #29
Dries CreditAttribution: Dries commentedI think I found a bug: when I update the path of a custom menu item, it doesn't get stored.
How to reproduce: I created a custom menu item 'test', with the path 'user/1'. I then tried to change the path to 'node/1', and it doesn't get updated.
(It's no longer possible to create new menus?)
Comment #30
Dries CreditAttribution: Dries commentedAlso, the primary iinks are not longer available?
Comment #31
chx CreditAttribution: chx commentedNo menus being primary or not -- for now, I wanted to move in small chunks. Fixed the update problem, it was rather trivial, just left out the path column in UPDATE. Made phases into defines.
Comment #32
chx CreditAttribution: chx commentedMore comments and better security practice.
Comment #33
Steven CreditAttribution: Steven commentedCommitted to HEAD.
Comment #34
(not verified) CreditAttribution: commented