I've just begun experimenting with this module and so far am very pleased with how it is working. Our website uses very basic and simple html that processes very well. I do have a question about image and other file handling. Many of our pages and images are directly linked from outside of our website. The import retains the html page link paths very nicely, but by insisting on moving files into another area it will break image links from outside of our website.

If I have html and jpegs in this folder structure: folder1/folder2/folder3/ the paths to the html files will remain the same but the image files are more likely to show up in something like: sites/files/imported/folder1/folder2/folder3/ -- thus breaking outside links. How do it tell it to create a path directly under the root?

Comments

dman’s picture

dman commented
Status: Active » Fixed

In the settings,
[ ] Relink references to resources to the new file storage location
As the actual files are being stored elsewhere, the HTML links need to be rewritten to allow for that. This should be on by default. Turn off only if you are intending to re-create a messy site with files in old places and have set the file storage path to blank. See the transformation file rewrite_href_and_src.xsl for fine-tuning if there is trouble.

teschek’s picture

teschek commented

I did see that but I can't seem to create a blank value in the path. I get an error message stating "The directory does not exist."

dman’s picture

dman commented

That may need work then. Possibly not tested since Drupal 4.

teschek’s picture

teschek commented

Hmmm. That would be unfortunate. Does that mean I'm out of luck, or is there a chance of getting it fixed any time soon?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

teschek’s picture

teschek commented
Status: Closed (fixed) » Active

I'd like to revisit this. Is there any chance of getting a fix to this issue?

teschek’s picture

teschek commented

Hello. Still wondering if it's possible to get a fix for this.

dman’s picture

dman commented

I just tried it. Works for me on 6.x-1.0.
If you want to indicate the 'current' root directory, you can use just '.'.
All imports will happen directly on top of your existing Drupal site.
Take care they don't conflict with drupal files and folders.

Sorta bug emerged however:
It seems that it it leaving the 'tidied' html files behind, and it really should have been deleting them once it was done. this is a bug.
Having temporary tidied files nearby in the site directory is confusing, and can screw up apaches attempt at content negotiation. THis probably needs looking at.