I am finding that menu items only get created for pages in subdirectories: all of the successfully created menu items have paths of the form x/y. E.g. if I import /about.asp, I get the error "Looping menu path..." and no menu item is created. Here's what happens with debug enabled:

Path is now about
Looking for a menu item matching path 'about'
Looping menu path, this is either a recursion error (illegal paths), or caused by creating a new menu tree from the bottom up and we just reached the top. Although a menu structure for this page is now built, it may be hard to navigate to child pages if the parent doesnt exist. This can be fixed by importing the parents or creating section header content.

It seems that in import_html_create_menu_path, $path = 'about', $p_path = dirname('about') = '.' . So the test:
$p_path == dirname($p_path)
succeeds because dirname('.') = '.', hence the "Looping" error.

Version info:
---------------
import_html 4.7.x-1.x-dev Last updated: November 13, 2006 - 12:19
@version $Id: import_html.module,v 1.23.2.1 2006/10/08 14:44:20 dman Exp $
Drupal 4.7.4
PHP 5.1.4
Mac OS 10.4.8

Comments

dman’s picture

dman commented

Good tracking, thanks.
yep, if dirname('about') = '.' then this maqy be a special case to be aware of - I probably expected empty string.
My testing has always been making a parent menu root first :-}

Should be fixable...

dman’s picture

dman commented
Status: Active » Postponed

Unable to replicate, and I've been doing a few top-level imports recently.
Can you explain a test case scenario that caused it? Or has it just gone away?

dman’s picture

dman commented
Status: Postponed » Closed (fixed)

Cleaning up issue queue by closing stuff from the Drupal-5 branch and over a year old.