Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I am looking at using this module to support a major site migration. The static HTML files would serve as the legacy version of the website to maintain Google ranking and incoming links. The failing, here, is that the node URLs are all renamed as .html files (site.com/url-alias becomes site.com/url-alias.html), so the old links cannot be maintained.
My suggestion would be to instead create a DIRECTORY for each node, named with the same URL alias, and then put an index.html file within that directory. (site.com/url-alias/index.html) This would maintain the original link, and maintain a 100% static HTML site.
Comments
Comment #1
btopro CreditAttribution: btopro commentedHmm... this is a very interesting solution. I don't think I'd accept a change in the way it worked to act this way but this would be a nice checkbox kind of option. HTML_Export really shines when pulling a site down locally and then exporting on your local box. After that you can put it back up on a server.
For what you're talking about you might want to look into Path redirect http://drupal.org/project/path_redirect
Comment #2
matteoraggi CreditAttribution: matteoraggi commentedyou could use token to add .html to the urls and keep track o the changes trough http://drupal.org/project/pathauto
Comment #3
jenlamptonI think creating an HTML export with 100% broken links is a bug. Changing status.
Comment #4
btopro CreditAttribution: btopro commentedyou're welcome to submit a patch for this functionality though this works fine in a localhost environment, where it was intended to be deployed.
Comment #5
btopro CreditAttribution: btopro commentedpaths should be handled correctly now regardless of location in 2.x branch. If not, you can reopen from there
Comment #7
jenlamptonThanks @btopro