Closed (duplicate)
Project:
Drupal core
Version:
6.x-dev
Component:
menu system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 May 2007 at 16:07 UTC
Updated:
29 May 2007 at 23:19 UTC
Jump to comment: Most recent file
Comments
Comment #1
pwolanin commentedinitial work on conversion- nothing in menu module works yet.
Comment #2
pwolanin commentedslight rethinking.
Comment #3
pwolanin commenteda start on the code for blocks
Comment #4
pwolanin commentedper my discussion over e-mail with Karoly- I will handle primarily the code for menu.inc, while he'll work on menu.module, etc.
Splitting of the menu.inc part into a separate issue: http://drupal.org/node/145058
Attached is the part of the previous patch that is specific to menu.module and menu.install
Comment #5
pwolanin commentedJust trying to think about how the install/update process will run.
I think it makes sense to have the update code as part of system.install? I guess it could be in menu.install instead?
I think 'menu' should be added here in default.profile:
Comment #6
chx commentedWe have a new , much more logical arrangement for admin/build/menu , menu add/edit works, menu item add/edit works, enable/disable works. There is an untested attempt at blocks. Will be finished today, I hope.
Comment #7
chx commentedBetween two parallel patches I lost some code. This one indeed does: add/edit menu, menu item, enable/disable menu item.
Comment #8
chx commentedmodule only patch
Comment #9
chx commentedtypo fix
Comment #10
chx commentedmodule only...
Comment #11
chx commentedSo very hard to work without http://drupal.org/node/145058 committed.
Comment #12
joshk commentedThis patch is actuallly required for http://drupal.org/node/145058 to work, as I just discovered.
Also, you missed a reference to menu_get_root on line 648, which is the settings form.
Comment #13
chx commentedI opened another issue... i forgot about this one.