Very excited about this module - I currently use FUpload, but it is just plagued with problems and not a very clean solution.

Switched my CCK image field from FUpload to Uploadify and enabled it. It appears to work - images are uploaded, but upon saving the node no images are attached. Are there any steps or requirements I could be missing that are not outlined on the module page?

Cheers.

CommentFileSizeAuthor
#9 Screen shot 2012-01-18 at 8.53.16 AM.png65.11 KBcraigmc
#4 before uploading two files.jpg15.64 KBjwaxman
#4 after uploading two files.jpg22.24 KBjwaxman

Comments

dsnydernc’s picture

dsnydernc commented

Upgraded to the latest Dev and it does work, kind of. It attaches (approximately) 1 in 10 images to the node. This module looks fantastic, can't wait to ditch Fupload for Uploadify... when it works.
Thank you for your efforts. Cheers.

Krummrey’s picture

Krummrey commented

I have the same problem where the progress-bar will go to 100% but the images are not atteched to the node. I.e. they do not appear in the list of images. This happens most of the time, not always however. 1 out of 10 seems about right. So I can confirm this issue.

makara’s picture

makara commented

Thanks for testing.

Can I have your settings and if possible, a screenshot?

jwaxman’s picture

jwaxman commented
StatusFileSize
new after uploading two files.jpg22.24 KB
new before uploading two files.jpg15.64 KB

Thanks for working on this. We need this module badly.

I guess I'm having similar problems.
I'm using this on a filefield rather than an imagefield
A few issues
1) The Browse Button doesn't activate the filebrowser unless you click on its left side.
2) Uploading files results in the already attached files disappearing from the table of attached files.
3) Uploaded files don't usually don't appear in the list of files and don't get saved with the node.
Two screen shots attached.

Please don't give up. This work is and will be very much appreciated.

Krummrey’s picture

Krummrey commented

When I try to upload 10 images:
Only local images are allowed.http://img64.imageshack.us/img64/8398/bildschirmfoto20100208u.png

Only a few (here 3 out of 10, sometimes less) are inserted into the CCK Imagefield:
Only local images are allowed.http://img130.imageshack.us/img130/8398/bildschirmfoto20100208u.png

The others are uploaded but are stuck in the queue
Only local images are allowed.http://img64.imageshack.us/img64/4815/bildschirmfoto20100208un.png

My settings:
Only local images are allowed.http://img693.imageshack.us/img693/8398/bildschirmfoto20100208u.png

dsnydernc’s picture

dsnydernc commented

Ditto on Jan's screenshots and behavior, though I haven't had the stuck in queue issue since upgrading to the latest CVS build. Also ditto on jwaxman's request; Drupal needs this module BADLY. Please don't give up, and we all really, really appreciate your fine efforts! Fupload is a f'ing disgrace to modules and workflow; this is has the potential to be the disney land of uploading for all of us so, so desperate for it!! =)

bennos’s picture

bennos commented

@jwaxman

filefield module uses pecl extensions (apc or uploadprogress). APC has several bugs in the upload function and could be missconfigured. typical the tmp path is not writable or does not exist.

Look in the config of APC or better post a PHP info output. It sounds more like as enviroment problem, then al problem with uplodify.

Dandily’s picture

Dandily commented

I had the same problem - images uploaded to 100% and then stoped, without adding to node.
I switch off Devel and everything is ok now!

craigmc’s picture

craigmc commented
StatusFileSize
new Screen shot 2012-01-18 at 8.53.16 AM.png65.11 KB

I'm having a somewhat similar issue--
I select 5 images
Uploadify correctly uploads 1 of them, then it stops hiding the progress bar and adding the image to the on-screen form's list of image. It simply overwrites the 2nd image so I wind up with Image 1 and Image 5 getting added to Drupal.

Note: the uploads themselves actually work, e.g. I see image 1-5 in the /files directory, it's just at the SWF/Javascript handoff where for some reason the on=screen form isn't getting the info it needs to work properly