Support files uploaded, but not yet submitted via node

HI

We already had a similar idea and ulink_gallery address that. For instance, you can upload all your trip photos to a directory called files/trip_photos and automatically display all the images by [l|files/trip_photos|My trip photos|class=my_gallery_css]

*please refer to the settings page of ulink_gallery which is under ulink settings >> image settings for submitting a class

The only restriction here is that folder should come within files folder, to make sure we can freely traverse through it.

However, if you wanted to add a comment for each photos you are out of luck with this module, since this only collectively handles the photos.

But I have written an extension to uAuto, which extends the capabilities of ksearch functionalities and it allows users to type
[l|files/my

where ''my'' is the directory
and they will be given list of filenames (files under files/my directory) to choose what to come next. (I think this is what you expected).

Again this feature is restricted to anything comes withing ''files'' although recursive search is available by default which means, if you just specify files you will offered with all the files coming under that.

Thanks for your interest in uLink

Between I m releasing the final version today, thats why it took sometime to reply this thread

Sorry to reopen, but I'm still a little confused. While your reply is helpful (good to know I can upload a batch of files to a folder within /files and have them available), it'd be nice if the module could find images just uploaded (still in tmp directory). Without this, I have to upload an image, submit the node (so the file gets moved from /tmp to /files), and reedit node for the file to be found with uauto.

If it's not possible to traverse through images in the /tmp directory, then I can understand -- but I think that's what I meant my request to be.

Hi again sorry for the late reply.

Can you please explain how you are uploading your files. If you FTP the files (which I normally do and prefer instead of normal upload through Drupal) you can FTP anywhere, so by doing that to any directory inside "files" you can use ULINK and UAUTO to refer to them.

But I think you meant something else. Here, to be identified, the files you upload need not be in files directory, we are completely overriding that, and only through directory traversal we find the files (for the ULINK_GALLERY and UAUTO_dirsearch). So files you uploaded are not restricted to a node .. or you don't have to create a node for that.. Where ever you wanted the images to appear use ULINK_GALLERY - for collective display with single line of code or UAUTO_dirSearch - for individual display of image with autofind )

Hope it helped.

Please reply to this thread to contact me at garthee AT gmail DOT com for further clarifications.

I'm uploading files via an CCK imagefield and the Drupal code Upload module.

In terms of non-tech users, they won't be using FTP to transfer files -- instead they will be uploading 1-2 new files via the node edit form. What I would like to see is the ability for this module to be able to traverse through the files that are uploaded via the CCK imagefield (thus still not actually uploaded to /files/ as the node hasn't been updated) without having to submit the node and re-edit it.

Hello bsuttis,

I will look into the possibility. But I see only a very remote connection with the particular need and the problem ULINK addresses. For ULINK, we expect the folder be completely accessible (typically files/ ) or user be aware of the location of the file (ie providing complete URL to ULINK)

I am not sure how CCK image upload is handled, but I gather it is uploaded to tmp directory (from the previous post). But I believe allowing users to upload images through FTP is a valuable addition for drupal and possibly other modules should consider that :)
and in my case, without ULINK and UAUTO i would be having hard times in sharing my photos at my site :)

Thanks -- I agree that the 'upload via FTP' option is very valuable for large batches of images, but my non-technical users simply don't have FTP programs or the will to learn how to use them. Being able to access images stored at /tmp/ would be a massive help to node workflow (and to answer your question -- yes, CCK imagefield images are stored in /tmp/ before the node's updated, just like Drupal core uploads).

I know that the /tmp/ uploads are stored in the sessions database table in what appears to be a serialized form, so maybe something like unserializing and traversing though the sessions 'session' column and picking out the relative file path would allow this to work...