I've just installed the latest (non-CVS) image, and Drupal 4.7.3

Here's the problem I'm having... Image module gets enabled with no problem, I'm able to get to the Add New Content -> Images with no difficulty. Only, after adding an image, it does NOT display. I viewed the HTML source and noticed that the PATH is incorrect.

  1. The images are being generated correctly, and stored in the path I specified, similar to public_html/files/images -- yes, permissions are correct, and writing is allowed
  2. The path when attempting to display an image node ends up looking like this:
    http://www.example.com/system/files/images
    which of course ends up with no images displayed, as there is no "system" folder.
  3. This happens whether or not I've set Files to be private or public.
  4. Yes, I do NOT have a trailing slash.
  5. I've got mod_rewrite enabled and functional, and am using friendly URLs.

Where did the "system" come from? It certainly doesn't exist anywhere on my server, and I'm unable to locate any settings page within Drupal where this might be corrected.

Any ideas?

Comments

styx’s picture

I have a similar set-up with Drupal 4.7.2.

All images, including previews and thumbnails, are in files/images relative to the Drupal folder. All links in the generated pages are of the form http://www.example.com/system/files/images/... , and all the images appear correctly despite there being no "system" folder.

So I suspect your problem is not related to the paths.

ob3ron’s picture

kbrune, I'm experiencing the same thing. Any progress? I'll post back here if I discover a fix.

ob3ron’s picture

I found a workaround:

In administer > settings > file system settings, I changed the File system path to "files" (without the quotes) and changed Download method to public.

Not sure yet whether this is going to cause other problems though.... if you don't hear back from me then I guess it worked! ;-)

sun’s picture

Status: Active » Closed (won't fix)

Development and support for 4.7.x and 4.6.x has ended. You are strongly advised to upgrade to Drupal 5.x or 6.x.

Marking as won't fix.