Posted by BWPanda on May 2, 2009 at 11:29am
4 followers
Jump to:
| Project: | jUpload for Imagefield |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
When I upload images with this module, the page refreshes to show the images in their respective imagefields, however, all other CCK fields I've entered stuff into are blank.
I think this is a bug in the way this module refreshes the page as I'm sure other modules do this better...
Comments
#1
You are right. At this point the module does not handle other cck fields well. If you really need to use this module, for the time being you should save your node first, then edit again and update your other cck fields.
Otherwise I recommend image_fupload, which is probably a better module to use anyway.
#2
Thanks, for the meantime I'll just make the image uploading the first thing I do when creating a new node.
I did try FUpload first, however, found it to be a bit buggy... I also like the way your module integrates fully with ImageField - the images actually appear in the ImageField fields once uploaded so you can enter Titles, etc. FUpload takes you to another page to enter 'captions'...
#3
I don't know if it's related or not, but I have jifupload working perfectly on one website, but it won't work on another. I updated filefield & imagefield, (latest as of may 7th) and after I upload the images, the page refreshes, erases the title and body, then tells me that the alias is already in use and changes my title to "temporary title - replace this title" or something to that affect. I'm sure it has something to do with pathauto as well, but I also noticed that uploading images with a tokenized path, (filefield path is not enabled), the tokenized path is not recognized... jifupload would either upload to the folder before the token path or create a new folder with the token naming convention, instead of the actual tokenized path. (Example: /images/[site-date-yyyy] should be 2009, instead it outputs /images/site-date-yyyy) I dunno if it has to do with filefield or jifupload at this point... Regardless, It appears that with the updates made to either filefield or imageupload, jifupload is not quite working right...
I will also have to agree with BWPanda on the FUpload... I love how jifupload seamlessly integrates with imagefield, unlike FUpload. Jifupload does things the right way, FUpload is coded to do things the "easy" way...
Otherwise, jifupload is a GREAT module!!
(on a side note, I was able to update the jifupload applet to 4.3.1 without any problems. Be sure to clear both the java cache and temporary internet files before attempting to re-load the applet.)
#4
I think we should move #3 to a new issue. I don't think they are related to this one.
Here's the main difference between jifupload and image_fupload:
jifupload does a node save after it adds the new images to the node, before it refreshes the page. But it Doesn't look for changes to all cck fields, so those are lost.
image_fupload appears to simply update the form and let the user do the node save, so any cck changes are kept. I haven't looked under the hood.
Personally, I'm using image_fupload on a large site over jifupload. The site editors seem to like it better and think it will be easier for end users to use.
I've been thinking about how to make jifupload preserve all cck changes. Maybe I'll have time next week to work on it.
Thanks for the feedback.
#5
Moved #3 by philsward to #458158: Jifupload not recognizing path tokens
Let's deal with his token issue separately.
I'll continue to look for a way to deal better with other cck fields.
#6
status change
#7
I have just stared using this module after having issues with the fupload module. On my CCK fields I have an auto node association field which is populated via a session value which gets removed once the upload is complete. Even though the node is created I have to edit it later to re-enter the associated node title again. Fiddly but better than nothing. Looking forward to not having the page refresh...