During my upgrade to Drupal 6 & upgrade of imagecache. I had trouble with uploading new images. All of my old images were fine, but newly uploaded images did not appear.
I then discovered that
Imagecache created a second files folder within the my sitename.com/drupal/files
named files - so it is sitename.com/drupal/files/files
However,
When I set the admin>settings>file-system to files/files
The images do not appear
Also, I am unable to set the file permissions to this new files folder as the UID & GID of this folder and interior files is Apache.
I've been looking for a way to fix this via the forums, but have not found the right node. Please help me to discover how I can correct this issue.
I
Comments
Comment #1
cpapaya commentedable to change the UID & GID & allowed to set permissions for /files/files & files/files/imagecache to 777
However, I still see no images when I set the admin>settings>file-system to files/files
Did receive warning discussed in http://drupal.org/node/392100
However, when I did their suggestions (setting permissions to 777 and changing module code of line 555) I still do not see new photos.
Also, the files/files folder appeared again, after I deleted old mysite.com/drupal/files and reinstalled old files without the added files/files
Comment #2
cpapaya commentedComment #3
cpapaya commentedchanged the files/files to files/uber
images show now. however, some photos is in the admin area do not show.
can deal with this, as long as images on site show
Comment #4
Robert S commentedHad the same problem: new uploaded files are added to files/files. I have no clue,
whether this is a bug or feature.
Renaming files/files to files/uber did not work for me, the directory was created again.
What solved the issue for me was changing the rights for the files/files folder
to no rights for anybody. (Not even the owner can read it, chmod 000 files/files )
Now the files appear dutifully in files, as they (I believe) should.
Still, this should be fixed ...
I suspect the module FileField is the culprit, so I am changing the status accordingly.
Comment #5
quicksketchI've never heard of this report before in nearly a year that FileField 3.0 has been out. I don't think this is caused by FileField. I'll need a report of how to reproduce from a clean Drupal install.
Comment #6
bstrange commentedSame problem... setting the second files (i.e. files/files) did the trick, still somewhat concerned...
Thank you kindly Robert S
Comment #7
furamag commentedI don't know why but I have this bug because I have incorrect configuration on my Drupal DB. To fix this bug you should go to /admin/content/node-type/{type_of_your_node}/fields/{field_name} and set correct File path in Path settings section . If your file path is "files/folder1/folder2" you should set "folder1/folder2" to field File path. It works for me.
Comment #8
ludde_t commentedFuramag's right, somwhere in the dr 6 migration "files" had been put in the path settings field on my node types that's using filefield. Removing the "files" path solved it for me. Thanks!
Comment #9
quicksketchI can't find this problem anywhere within FileField. Are you guys using any other modules that might be affecting the file path? FileField Paths for instance or another add-on?
Comment #10
quicksketchUnless this can be confirmed as a problem with FileField, I don't think there's anything to be done here. FileField doesn't ever touch the "file_path" setting in any of its upgrade routines. ImageField's upgrade path is similarly simple (from imagefield.install):
I really can't see how this would be caused by FileField. However if I'm mistaken please reopen.