File Attach v. CCK Fileframework Field [#630386]

I've enabled the CCK field module for Fileframework, and I've created a content type with a CCK File Field.

When I try to enter a file in the file field, it only allows an upload. There does not appear to be any way to enter a file already in the database in the field (like I can with file attach). Is this how it is supposed to work?

Whether that is the case or not, what advantage is there in using a CCK field instead of the file attach method? Could you give me an illustrative use case where it would be better to use CCK file field instead of the fileframework attach mechanism? I can't understand when I should be considering CCK fileframework field instead of fileframework attach on a node.

Comment	File	Size	Author
#5	filereference.zip	14.81 KB	jvieille

Comments

Comment #1

miglius commented 16 November 2009 at 23:14

Attaching existing files is supported only bu the file_attach, not the file_ckk module.

File attachments are listed in the table which is displayed below the node. Cck file field can be themed to appear anywhere in the node.

Comment #2

Th30philus commented 30 November 2009 at 18:45

Status:

Active

» Closed (works as designed)

I think I've figured out a way around this with CCK. Instead of creating a file field, I create a node reference to the File content type. That allows using existing files, and if the file does not already exist, I can create another File content for the new file.

Comment #3

jvieille commented 7 April 2011 at 22:06

Category:	support	» feature
Status:	Closed (works as designed)	» Active

Is there any reason CCK field cannot attach existing nodes?
The CCK field offers 2 main advan tages
- it allows some choices to displaying the files inside the node
- it allows to define specific sets of files within the node. For example, I have content type for managing pieces of software. It contents a set of "specifications" and a set of "code" documents

It would be great if this feature, which is available for the normal attachment, was granted to the CCK field

Thanks again for this great module

Comment #4

jvieille commented 11 August 2013 at 07:27

Priority:

Normal

» Major

It is worth to note that uploading several times the same file for different cck fields only keeps one single set of bitcache files as they are identical.
However, when uploading a modified file, the change is not propagated to all the nodes previously created for each occurrence of the cck field.
This is a really annoying issue.

Comment #5

jvieille commented 12 August 2013 at 19:49

Component:	Documentation	» Code
Status:	Active	» Needs review

Status	File	Size
new	filereference.zip	14.81 KB

Attached a new module that provides a usable CCK "File reference" field.
This module is a straight copy of the CCK Node Reference module modified as follow
- no node type selection: it takes the "file" node type as a standard and only node type
- views selection is still available- of course, this will only work with file nodes.
- all File Framework handlers are available as node and views display
- relationships should work, so it is possible to create files at the reference time.

I have doubts on the .install file : I kept what was in the current Node reference module,though everything might not be necessary.

This deprecates the current file_cck module, though they perfectly work together.