HTML Export creating empty (size=0) index.html files

hmmmm. What's the site address, are clean URLs turned on, and what happens if you just select nodes as the thing to export

Hi, I had the same problem,
I work with drupal 6.25 install on localhost, mac os X, powered with Mamp

In /all/modules/html_export folder,in the file html_export.pages.inc, at line 163, the path provided to drupal_html_request() is not correct. More precisely, the value of $root in html_export_render_pages() is "/", which is not correct.

My root instalation is http://localhost:8888/ ; Then I replace the lines:

//$http = drupal_http_request($root . $paths[$active]);
whith : $http = drupal_http_request("http://localhost:8888/" . $paths[$active]);
and
//$http = drupal_http_request($root .'index.php?q='. $paths[$active]);
whith: $http = drupal_http_request("http://localhost:8888/" . 'index.php?q='. $paths[$active]);

This changes fixes the issue.

However, another issue comes up.
If in a page .../node/3 ,I have an http link to ".../node/1", then this link is transformed whith the HTML_export into
/node/3/1 and raise a "file not found" error. It should be
/node/1

Thinking the issue might stem from my use of the #_SERVER["address"] property which might not be being set (how root is calculated). I think drupal_http_request requires a full url in order to process. Anyone know of a better way of verifying the site address that requested itself as the root to publish? I guess I could add a field to the UI to set the root manually and prepopulate it with whatever server value should (usually) work.

Possibly server value is not populated as per the comments above. I run this in production and localhost without issue so not sure without a lot more info.

Look for where that property is referenced in the module and hardcode your address and see if it works. Not all servers have that property set i'm finding and that's a large part of the issue. The module issues a drupal_http_request to the full address (which it needs) and basically spiders itself with "remote" requests coming from the site itself.

I changed that line and worked for me.

$root = 'http://localhost'. base_path();

the installation located in some where in localhost

yeah, i think I need to make a way of setting that in the settings as to what the base address should be. I can guess at what it should be via the server value or some js trickery in the URL on page load but will still need to set it manually it appears to ensure that it works... I would want this to happen in the admin settings page and would accept a patch for it or I'll get to it at some point.

solution is now in git should publish to dev branch tomorrow. Now using global $base_url variable. You can set this in your sites's settings.php file to define the address for your site. HTML Export will then use this address to perform its query against. Have created multiple packages this way with web accessible addresses.