Hi

When viewing the node type "image", i can't see the actual image. The node is not displaying. After a long, long search I found out that in the html-code it actually gives the wrong path:

img src="system/files?file=files/IMG_0634.jpg

when I would expect:

img src="system/files?file=imagefiles/IMG_0634.jpg

or even

img src="system/files?file=files/imagefiles/IMG_0634.jpg

This seems to me to be a bug somewhere in the function that calls the path.

background:

  • My folder for images has been set to "files/imagefiles" (setting: "imagefiles")
  • img_assist is working fine: image files get uploaded to the correct folder.
  • 'personal blog' node types can be viewed no problem INCLUDING image or thumbnail.

check it out at my site

grtz

Hans

Comments

dekkeh’s picture

in addition it's worth noting that upload with img_assist and the image module itself, yields the same results.

And the database-field 'files' very strangle contains the correct pathinfo: "imagefiles/p1010030.jpg".

sorry about the bad link in last post. it's http://www.hansdekker.com

Hans

dekkeh’s picture

boy I wish I could edit those posts. Of course I meant STRANGELY.

Bèr Kessels’s picture

So, just to confirm:
is this appearing ONLY when you have the file system set to private?

dekkeh’s picture

I only tried it with the 'private'-setting because

"You can change this at any time, however all download URLs will change and there may be unexpected problems so it is not recommended."

So I'm afraid to change it to public.

Do you think this might have something to do with me changing it in the first place? I don't remember when I did it, but the behaviour also happens with entirely new posts.

BTW, if you look on my site now the links will work because I manually moved the pictures to the files folder.

H

Bèr Kessels’s picture

just try once with images set to public.

dekkeh’s picture

Change, but not for the better.

link to image changes to:

http://www.hansdekker.com/files/files/IMG_1702-1.jpg

Hans

drachenreiter’s picture

Hi,

I have a similar problem. It looks like that, if I open the image node the system trys to show the pictures (at least for some ms you see the frame of the picture with the right size and alignment) after these ms just the node frame with headline etc is shown.

If I try to see the picture via the link "view original" the same is hapening. If I activate the listing of the pictures, preview and thumbnail and try to access these via the links I just get a failure message saying:

The graphic "...../?q=system/files&file=images/*.jpg can not be shown, because it contains failures

The folder with the pictures "system/files/images/*.jpg exists (or actually the folder "system/" is linked to the folder "files/") and is found by the system. As well the watchdog does not show any failures.

Any clue what this could be?

andysmart’s picture

the same problem is happening to me, it seems images and theme editor folders are protected and I can't change their permission from 740 to 755. When I try to change permission the server says ti changed them but then they're still 740.

And if I try to see the subfolders of /files/images/ I get this error:
Unable to change directory to /home/skatecof/www/words/files/images! You do not seem to have access permissions! (System Error: Permission denied)

I also checked /files folder, but that is with permission 755 and the other drupal modules seem to work fine

dekkeh’s picture

I'm sorry but this is not the same problem I'm having. You need to chmod the folder or have your admin chmod it. You cannot access it because Apache created it itself through Drupal. A workaround is to create a folder yourself FIRST and then tell drupal where it is...that way it won't be created new. This is a small bug in Drupal that you can find lots of information on in the forums.

Again, I am having a different problem: in my case drupal is generating a wrong string for the location of the imagesfolder.

Ltr

Hans

dekkeh’s picture

After having the same problem after a reïnstall, I discovered Drupal/image has a problem when I create my own "files/images" folder. When I deleted the folder and let the image module create it's own "files/images" folder the problem was gone.

When I created the folder my self, I chmodded it to 777.

Strange but true, so solved for now.

Hetta’s picture

Status: Active » Fixed

This should have been marked "fixed" almost two years ago.
(I'm cleaning up the issue queue).

Anonymous’s picture

Status: Fixed » Closed (fixed)