Warning: Invalid argument supplied for foreach() in theme_links()

I'm getting the same error. Any solution?

I have the same error and it happens in framework_preprocess_page() in template.php. I'm using a sub theme.

My fix was to delete all functions from template.php copied from the original template files leaving only
<?php

Maybe deleting the file altogether if you aren't using it will work too.

I was accustomed to renaming functions with my own theme name, maybe template_preprocess_page() has an issue being redefined in the same way twice... I dunno.

In the parent theme, template_preprocess_page() passes the array $vars['main_menu'] to theme_links__system_main_menu(), and then overwrites $vars['main_menu'] with the resulting string. The subtheme comes with the same code, except now instead of being an array, $vars['main_menu'] is a string, hence the error.

Core and Zen get around this by calling theme_links__system_main_menu() directly in the page.tpl.php, which isn't necessarily the best solution. One way to fix this would be something like this:

In the parent theme:

if (isset($vars['main_menu'])) {
  $vars['main_menu_links'] = $vars['main_menu'];
  $vars['main_menu'] = theme('links__system_main_menu', array(
    'links' => $vars['main_menu_links'],
    'attributes' => array(
      'class' => array('links', 'main-menu', 'clearfix'),
    ),
    'heading' => array(
      'text' => t('Main menu'),
      'level' => 'h2',
      'class' => array('element-invisible'),
    )
  ));
}
else {
  $vars['main_menu'] = FALSE;
}

In the sub theme:

if (isset($vars['main_menu_links'])) {
  $vars['main_menu'] = theme('links__system_main_menu', array(
    'links' => $vars['main_menu_links'],
    'attributes' => array(
      'class' => array('links', 'main-menu', 'clearfix'),
    ),
    'heading' => array(
      'text' => t('Main menu'),
      'level' => 'h2',
      'class' => array('element-invisible'),
    )
  ));
}

I see. The next version of Framework will use the default method of rendering the menus. The D6 branch already does this, and the next release of the D7 branch will be identical to what is found in the "Stark" page.tpl.

fixed in 3.6

Please read over http://drupal.org/node/52287, it explains how to write proper commit messages. Each fix from each issue should have a separate commit with a descriptive message.

Yeah, my working habits are probably not too great in this regard. Currently, I make changes as I see fit, address any open issues, and generally get the new incarnation into a state that's release-ready. Then I write up a rough list of changes, and commit the whole thing. That probably sounds nightmarish for thorough developers and users. I'll change my ways after I push this D6 port of the 7x branch.

Thanks elpino. Deleting everything except "<?php" in template.php did the work.