Closed (fixed)
Project:
Image FUpload
Version:
6.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Mar 2009 at 17:31 UTC
Updated:
1 Apr 2009 at 21:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
demm commentedMake sure your "File system path" and "Temporary directory" (/admin/settings/file-system) are both writable by the webserver.
If you have CCK's content_permission module activated, you also need to set "edit field_images" (or whatever your imagefield is called).
What exactly do you see when you try to upload the images? (Take a screenshot if possible)
Comment #2
mrthumpz commentedYes they are both writable, and they work for user1.
No, I don't have the content_permission module enabled.
Attached are screenshots - the first represents what it appears like after the upload bar progresses across the screen (Error 403), the next item starts to upload, but they will all get the same error. The second image is how it appears after waiting for each image to fail.
Comment #3
grandcat commented(Something has to be wrong with your server settings, because I did not change anything concerning the flash uploader.)
Another reason could be, that I changed some theming related stuff what means that you have to reinstall image fupload and its submodules because the data which needs flash to access to the server, changed.
Comment #4
mrthumpz commentedHow could it be server settings if it is working for user1?
Ok, I installed a fresh Drupal site, an re-downloaded the module and the swfuploader.
It is still doing the same thing, here is what is entered in the log when this is occuring:
Type access denied
Date Monday, March 16, 2009 - 22:38
User todd (this is not the admin)
Location http://test2.iplanitglobal.com/fupload/flash
Referrer
Message fupload/flash
Severity warning
Hostname 72.241.207.9
Operations
What else is interesting is if I click on that /fupload/flash link as an admin, it tells me access denied and logs me out.
Any other ideas?
Comment #5
robertdjung commentedI'm getting this error, too. I have un-installed and re-installed. Same as first user, User#1 admin account works flawlessly. Any other user doesn't.
Comment #6
mrthumpz commentedgood to hear someone else was having the problem too...
-Mugatu
Comment #7
demm commentedDo you use any kind of access module (i.e. taxonomy access)? Try rebuilding your permissions (/admin/content/node-settings).
If that doesn't help, try disabeling that module.
It could also have something to do with caching. If you use it, disable it and flush all cashes.
Comment #8
mrthumpz commentedI figured out what the issue was. For the user I was using, I granted them administer nodes permission, but none of the create, delete, edit permissions specific to each content type. It worked when I gave the user 'create photo_gallery content' permission.
This shouldn't have to be required - 'administer nodes' should trump all those settings.
Comment #9
demm commentedYou're right, 'administer nodes' should give full access, but the module only checks against 'create images' or 'create '.$node_type.' content'.
This should be considered a bug.
Comment #10
mrthumpz commentedComment #11
mrthumpz commentedsorry - we saved at the same time
Comment #12
grandcat commentedI don't think it's a bug. It's more a setting related issue which should not be a topic of image_fupload.
Comment #13
mrthumpz commentedReferencing: http://drupal.org/node/132202
Comment #14
grandcat commentedOK, thank you, I will change this in a future update.
Comment #15
demm commentedWell, I'm pretty new to drupal, but I think where your module has:
$field_access = user_access('create ' .$node_type. ' content', $user);it should read:
$field_access = node_access('create', $node_type, $user);node_access() will first do some checks (e.g. if 'administer nodes' is set) before invoking the module's (in this case CCK's) access hook.
I tried this change at my local test system and it worked like expected.
Comment #16
demm commentedsorry, forgot to refresh the page before submitting
Comment #17
robertdjung commentedmaybe this is changed in DEV, but as of alpha 3 I get the 403 error, even when the permissions are set to create specific node types, and edit the specific field.
Comment #18
grandcat commented@ robertdjung:
A reason could be, that I changed some theming related stuff what means that you have to reinstall image fupload and its submodules because the data which needs flash to access to the server, changed.
@ demm:
Thank you. I didn't know this function, but I will integrate it.
Comment #19
grandcat commentedFixed in CVS Head.