Normal pager doesn't work with menu

I can reproduce with a clean install and all core optional modules enabled.

I can reproduce this as well - the menu_links table appears to be OK.

Probably related to fact that it's two pages, and the child item appears on a different page from the parent.

Also -- Note that 'Recent posts' is on the second page, when it should be near the top of the menu tree.

More info:

It displays more pages than are needed. To reproduce only activate 'aggregator'.

menu_overview_form is passing an incorrect count of total items displayed to pager_query.

The pager cuts the rows based on the query and 'sources' is affected.

if the data is OK, but it's displayed wrong it may not warrant marking this critical, though it may totally ruin Drag-n-drop functionality

This is a *very experimental patch* (waiting chx to give an opinion) that resets all menu_links that are not customized or active.

Well, it's an experimental patch that works, on first impressions at least. On a 5.x-6.x upgrade, reproduced the extra menu items, ran update.php (with no updates, but all the way through anyway), and the extra items were gone from the admin panel. I'd been messing with menu drag and drop for the other js issue, so some of the old links were 'customised' and hence not deleted, but I'll try to do some more detailed testing later.

http://drupal.org/node/211359#comment-696623

The isn't a duplicate. And the patch isn't right -- that simply rebuilds the menu tree, reordering the records in the table making this appear to be fixed, when in fact the source of the problem is the pager.

I believe that pager most likely takes the first n items from the menu table for page 1, whether or not they belong on page 1.

I think webernet is correct about the pager (which I always had some concerns about). Prior to the drag-n-drop it was not as much of a problem since you had to go to a separate screen to edit the parent/weight.

To do this right, it really needs to be a custom version of the pager that makes sure that all the children of a parent appear on the same page with it.

I think that there are two problems here:

1) The count query passed is counting all the items and not the items that end being displayed (hidden, not active).

  $sql_count = "SELECT COUNT(*) FROM {menu_links} ml WHERE menu_name = '%s'";
  $result = pager_query($sql, 200, 0, $sql_count, $menu['menu_name']);

2) webernet is right on that the childs can be separate from parents because of the pager not knowning anything about families.

To solve 1) I would like to pass the total number of rows to pager_query with a number and we only need a menu function that counts active items.

  // We calculate the total of pages as ceil(items / limit) if a number is not provided.
  if (is_numeric($count_query)) {
    $pager_total_items[$element] = $count_query;
  }
  else {
    $pager_total_items[$element] = db_result(db_query($count_query, $args));
  }

To solve 2) yes a custom pager.

Marking "needs review" so you all look at it, though this is obviously not totally polished. Seems to work and to render all the top level links in the right order. Gobor or someone want to test with localized titles?

It is bad enough that we can't use the built in parent choosers because they display full menus but to display all children if a parent is visible is :( let's decide whether we want core to support big menus or not.

updated patch with one slight change to the code and lots of doxygen comments.

here's the alternative suggested by chx - just lose the pager.

Removing the pager completely sounds like the simplest and safest solution. It also fixes the issue of not being able to drag and drop over multiple pages. Hopefully the page won't get too big.

You can always menu_alter this page to your contrib module which does something better or just access FALSE this page and provide a totally alternative interface. With the drilldown parent choosers moved to D7 we already decided that while the backend provides support for insane big trees, the core UI does not. Case closed.

Tested OK.

This patch is the same as above, but I also noticed that this form builder doesn't store in any accessible place which menu it is working with - thus added an additional line.

+1 to no pager -- I found it to be annoying when moving one menu item to another page. Works better with DnD. :)

Well, since even Dries says we should remove the pager, I committed #21. Better solutions for big menus will hopefully be available in contrib.