Just had a a brainstorm that would make Asset really useful.

My problem with Asset, as all the different file-related modules I'm currently using Imagefield, Image, Upload (+Upload Path), maybe WebFM, ALL want to "own" the files they uploaded, and don't make them available for re-use except by just pointing to them directly with HTML tags in a text field (IMO a nightmare to maintain, what's the point of using a CMS?)

I know there are fundamental problems with having multiple nodes referencing a single fid row in the files table, hopefully to be fixed by the time D7 releases.

However, once I've figured this stuff out, and until that issue is fixed, I'm intending to NEVER delete any nodes or files from my sites. The only other alternative seems currently to be to have many duplicate versions of the same files scattered through the folder tree under files (yech).

So why not give an option for Asset Import to scan through the whole files tree and add ALL the files as Assets but LEAVE them in their current location?

Then I could use either the CCK field for theme-programmed placement, or the Asset tag syntax for placement in line with content. I assume both of these are just pointing via the Asset tables ultimately to the fid row in the files table, so if later on the filepath had to change all the existing nodes wouldn't need to be manually updated.

Perhaps this is completely impossible/impractical, but to my mind should at least be a future goal, as Upload/Image nodes/Imagefields will be with us for a long while yet, and I see Asset as potentially allowing us to centrally re-use if not manage the files already uploaded by these other modules.

Comments

dman’s picture

dman commented

Sensible suggestion, doesn't sound impossible to support.
I detest any file management software (client side or server side) that insists on taking ownership and moves my stuff around when I've already got my own structure happening.

HansBKK’s picture

HansBKK commented

I'm sure you (dman) are aware of this, but for others to follow:

So far in my testing Asset and WebFM are the ONLY ones that aren't detestable in this sense, and Asset's file browser has its own detestability (sp?) like not remembering my last selected location, always returning to "My Assets" which I'm not even using!.

Both Image and Imagefield just dump everything in one place.

Upload Path certainly helps with core Upload, but that's not much help for handling images (Inline requires the displaying node to be the attached node)

So if I could use Upload Path or WebFM to get the files up to the server where I want them to go, and then Asset let me use them for display in my nodes via CCK (theme-controlled placement) or via its inline tags, that would be a nice step forward. . .

dman’s picture

dman commented

Yeah, I don't mean to disparage asset module unduly.
Shall I just say I much prefer modules that don't behave that way without giving you a choice... :-)

wmostrey’s picture

wmostrey commented
Status: Active » Closed (won't fix)

This will not be fixed any time soon. Asset does indeed use its own folder structure and there is currently a feature request to allow setting the base directory that is likely to be implemented soon. However the idea of asset import is that you can also import files that not yet drupal files and that are uploaded through ftp for instance. These are moved into the asset base within the selected parent directory.