Closed (fixed)
Project:
Image
Version:
4.7.x-1.x-dev
Component:
image.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Jan 2007 at 09:47 UTC
Updated:
4 Apr 2007 at 06:01 UTC
When trying to create an image node, an error is reported. "The selected file /var/www/drupal/files could not be copied". But if i attach the image to the node, instead of creating it directly, it wokrs just fine.
Comments
Comment #1
Pewter Tankard commentedHappens with the 5.x-1.x-dev build too.
However... .a bit more evidence for you. This only happens for me if I go to Administer -> Content Management -> Content Types and edit the Image content type.
I'd gone there to remove the "Promote to Front Page" flag and, after saving these settings, I found that I couldn't create image nodes via the conventional Browse... and then Preview and/or Submit. I went back and reset this flag in the Image content type, pressed Save Settings and the same bug occurred. It was only when I went back to the Image content type and pressed "Reset Settings" that I got the correct functionality back when creating new Image nodes.
Hope this helps.
Comment #2
seanrHas anyone looked at this? It's been marked critical for a month and a half and has gotten nothing more than a "me too".
Comment #3
seanrChanged title
Comment #4
seanrThe Attach Images and Attachments options are both enabled by default when you pull up the image content type's settings page. Apparently that's just the default for the form, not what's actually enabled disabled until you hit submit, because having those enabled breaks the node's image upload. Those need to be disabled by default, and perhaps permanently for this type - at least Attach Images, since it's clearly incompatible. A user pulling up a content type settings page and simply hitting submit should never be able to break it but it will currently.
Comment #5
samo commentedI was bit by this too. Very frustrating to debug.
Can we have the defaults changed on install?
Comment #6
drewish commentedi fixed this in 5/HEAD. if someone wanted to backport the fix, please do so and re-open this issue.
Comment #7
(not verified) commented