Because Features module's "Create Feature" page shows all menu items (including disabled ones) for export, it makes the page very slow to load. It also make Feaures "Menu Links" export function unusable since there's hundreds or even thousands of disabled menu links to go through.

Can node hierarchy stop using the menu_links table in this way? Hierarchy relationship is already stored in the node_hierarchy table, why is it necessary to litter the menu_links table will disabled items? It's causing a lot of trouble in other places too. e.g cache_menu table My cache_menu table is 200MB, even my node_revision table is only 50MB. My database exploded 5x in size just because of this.

Comments

goofrider’s picture

Title: disabled menu links created by Node Heirarchy module makes Features module's "Create Feature" page very slow to load. » Please stop using menu_links table to store node hierarchy info
goofrider’s picture

Issue summary: View changes

expanding cache_menu problem

goofrider’s picture

Title: Please stop using menu_links table to store node hierarchy info » disabled menu links created by Node Heirarchy module makes Features module's "Create Feature" page very slow to load
goofrider’s picture

Or may I suggest that, at the very least, not adding an entry to menu_links table if a node belongs to a content type that doesn't have node hierarchy enabled?

goofrider’s picture

Title: disabled menu links created by Node Heirarchy module makes Features module's "Create Feature" page very slow to load » disabled items in menu_links table makes Features module's "Create Feature" page very slow to load
goofrider’s picture

Priority: Normal » Major
geoffv’s picture

+1

geoffv’s picture

Issue summary: View changes

Fix menu_links spelling