File

Finally got it working, well… sort of. When I try and upload mutiple images, I get this error in Firebug (within Firefox 2.0.0.9):

uncaught exception: [Exception... "Not enough arguments" nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)" location: "JS frame :: http://www.kirradive.com/system/index.php?S=07695b95125b3b2154821d099d0770c6f4a6e7e1&C=edit&M=edit_entry&weblog_id=2&entry_id=13 :: uploadFiles :: line 2451" data: no]

I don’t see an upload progress bar, despite uploading the new icon. It’s also only taking the first image and replicating it. This is the end result after update:

dc7f6d799a0eb827f30676090c7fd9f7.JPG dc7f6d799a0eb827f30676090c7fd9f7.JPG dc7f6d799a0eb827f30676090c7fd9f7_thumb.JPG dc7f6d799a0eb827f30676090c7fd9f7_thumb.JPG

So I get two copies of the first file uploaded (both original and thumb). What gives?

Thanks!

Hi Mark,

This extension is great but I also can’t see the progress bar when clicking save it just goes in as it normally would. Also if you can get this to work with the SAEF in the next version then I would walk across heaven and hell for you!! 😊

Thanks for such a great extension though and all the great work you do for us all.

Best wishes,

Mark

Mark, when I try to change my settings in the upload preferences, I get this error

MySQL ERROR:

Error Number: 1062

Description: Duplicate entry '5-show_thumbnails' for key 2

Query: INSERT INTO exp_mh_file VALUES('', 5, 'show_thumbnails', 'no') ON DUPLICATE KEY UPDATE id=values(id), `key`=values(`key`), value=values(value)

I have no problems with uploading pictures

I too was getting the same error as tpayton (working on 1.6.1)

MySQL ERROR: Error Number: 1064 Description: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘’ at line 1 Query: SELECT * FROM exp_mh_file WHERE upload_id=

I was able to get around it by disabling the extension and then adding new upload directories.

Once added, I re-enabled the extension and all works as you would expect it to. Thought it probably shouldn’t work this way, this work-around certainly should allow you to use the extension.

I’m using File 3.1.0 on EE 1.6.1. I’ve got a single upload field that I’m using for images. I’m resizing images uploaded via this custom field so that the width is 207px and the height is kept proportional. This works great but I’m getting some odd filesizes for the resized images. For example I uploaded a .jpg image which was 542px by 729px and 22Kb but the final image measuring 207px by 278px is 31.5Kb…

@benpowell - Hum, it must have something to do with the JPEG quality settings. I’ll take a peak and see what can be done.

Hi Mark,

I was just wondering if there was any news on using this with an SAEF yet?

Best wishes,

Mark

Mark - Coming soon, hopefully very soon.

Mark you deserve a medal.

Looking forward to it with baited breath! 😊

Hope everything is going well for you.

Best wishes,

Mark

Great extension, but a couple of issues using File 3.1.0 / EE 1.6.1:

1. When I go to File Upload Preferences and select the ‘Do not resize’ option, click on the ‘Update’ button and then view the preferences it doesn’t look like this option is saved as the drop down displays Auto as the resize option. All the other options seem to be save correctly.

2. I have an upload folder and when it’s set to images only the file uploads and its permissions are set to 777 but if I change it to all file types the uploaded file gets set to 600 so can’t be accessed via the public site.

Feature Request - Would it be possible to have an option so that where an uploaded image is smaller than the max width/height allowed in the folder and one of the resizing options is on that the image is not resized as currently images are scaled up.

When I go to File Upload Preferences and select the ‘Do not resize’ option, click on the ‘Update’ button and then view the preferences it doesn’t look like this option is saved as the drop down displays Auto as the resize option.

This will be fixed in the next version. It is saving properly, just not displaying the correct value within the select.

I have an upload folder and when it’s set to images only the file uploads and its permissions are set to 777 but if I change it to all file types the uploaded file gets set to 600 so can’t be accessed via the public site.

Strange, because my script doesn’t even look at the ‘images only’ option, so I’m not sure how that would affect things. I’ll keep an eye out for this behavior though.

Would it be possible to have an option so that where an uploaded image is smaller than the max width/height allowed in the folder and one of the resizing options is on that the image is not resized as currently images are scaled up.

Duly noted.

Regarding my post about uploaded files not being chmoded to 777 when the upload folder is set up to receive ‘all file types’ instead of ‘images only’, I think I found a fix (added code in bold):

// Do the Upload // ============================================= foreach($file_tmp_names as $file_key=>$file_tmp_name) { if(@move_uploaded_file($file_tmp_name, $server_path.$file_names[$file_key]) === FALSE) { $errors[] = str_replace(array(‘%{field}’, ‘%{file}’), array($file_field[‘field_label’], $file_names[$file_key]), $LANG->line(‘error_transfer’)); } else { chmod($server_path.$file_names[$file_key], 0777); } }

@benpowell - Thanks! I’m chmod’ing the thumbnails, but not the original. Silly me. This fix will get rolled into the next version.

I get the same error as tpayton upon making a new file upload destination. Using build EE 1.6.1 20071114 and File v 3.1. I got around it as well by disabling the extension and making the directory, then re-enabling it.

-snip- Post edited, because I figured something out. -snip-

Thanks for the continual improvement of this. The new stuff is fantastic!