Flexinode content types don't get attachment forms with attachment.module. They do get attachment forms when the default upload.module is enabled.

Is this a problem with flexinode or attachment.module? I tend to feel it's a problem with attachment.module.

Is there a way to have attachment.module hook into any code other modules have for calling upload.module? With attachment.module installed, one should have upload.module disabled, so it would be nice if attachment.module was a drop-in replacement (that added new features) for upload.module...

Comments

bomarmonk’s picture

bomarmonk commented

Hey, I would like to have this happen with the attachment.module also. I want to use flexinode to create a "file" content type, and use attachment.module so that titles will appear for each file... of course, I would like to also have the "attachment title" replace the required "node title." This eliminates a redundancy I do not need or want. How about it: can this be done? I really, really hope so... I like the way the attachment module handles file "titles" and need this for the site I'm working on. Any help would be greatly appreciated!

ccourtne’s picture

ccourtne commented

I don't use flexinode but I do know that one difference between upload and attachment and that is upload defaults to allowing attachments for all content types where attachment defaults to disabled.

Once you've created your node type make sure you enable attachments in the default workflow settings for that node type.

Craig

tostinni’s picture

tostinni commented

Well it works fine for me and flexinode, maybe it's a problem with the workflow permissions.

bomarmonk’s picture

bomarmonk commented

My misunderstanding was this: I expected the attachment generated from attachment module to show up in the flexinode field list when creating a new type of flexinode. Instead, you simply enable attachment through the content configuration here: /admin/node/configure/types/flexinode-10 (where 10 is the flexinode type with which you want to use the attachment module).

I'll change the status to "by design," and someone can reopen if there is really another issue that is a problem. Maybe this issue should be clarified in the documentation?