As I'm having a hard time using Filefield Paths together with Filedepot (see #1572170: Incompatibility with File (Field) Paths) I'm wondering if its somehow possible to disable Filefield Path on a per-field (or content type) basis? Filedepot works nicely when FFP is disabled and puts its file inside its directory structure, but all other file fields should be processed by FFP.

If I could somehow disable FFP processing for the field "filedepot_folder_file" everything should work fine.

Regards,
Daniel

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

piyuesh23’s picture

@Daniel,

I had the same problem. I have added an admin page to select all the fields for which we don't wan't ffp settings to be applied. Attaching the patch here.

piyuesh23’s picture

Sorry about the above patch missed the admin settings file. Adding the working patch here.

piyuesh23’s picture

Cleaned up the above code a bit and here is the final patch. Tested with couple of fields and it works like a charm..:)

piyuesh23’s picture

Added permissions for the administration of the filefield form.

Deciphered’s picture

Status: Active » Needs work

It would make more sense to me to have the setting on the Field settings page, a simple checkbox where the File (Field) Path settings are currently, that when toggled on will hide the existing File path settings and replace it with the File (Field) Path settings using the FAPI #states attribute.

This approach means it can be done on a field-by-field basis without the need for additional pages.

I would also say that it should be an on by default as off by default could confuse new users of the module and potentially break things for existing users.

Cheers,
Deciphered.

Deciphered’s picture

Version: 7.x-1.0-beta3 » 7.x-1.x-dev
Category: support » feature

Changing this to a feature request.

Deciphered’s picture

Status: Needs work » Fixed

An improved solution to this has been committed to 7.x-1.x.

Cheers,
Deciphered.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.