Visibility of custom File uploads in case activities

[Upperholme]

I have a custom activity type with some custom fields included, some of which are file upload fields. When viewing the case I can click on the activity to view it (which appears in a pop-up window), and the field labels appear, but I can't see the uploaded file links. I can see the file links when editing the activity.

I would assume that the links to the files should be visible when viewing the activity. Am I missing a config setting or this an issue?

CiviCRM 4.4.6 on current D7.

[demeritcowboy]

Do you have any custom code that might be overriding it?

[Upperholme]

Not that I'm aware of. No custom CiviCRM code, as yet. What we are doing is using Coleman's latest version of the webform_civicrm module which is enabling us to use CiviCRM file upload fields in the webform. I guess there's a chance that this issue could potentially stem from that approach.

But if I can see a linked file name when editing the activity, I should be able to see it/click it from the activity view pop-up, shouldn't I.

[demeritcowboy]

A couple of other things to check:

1. Does it work with a regular activity, e.g. a create a meeting and attach a file.

2. Are the directory entries correct, on the admin screen under system settings - directories and in civicrm.settings.php and in the database in civicrm_settings (I'm actually not sure where the definitive place is in 4.4 - I haven't kept up to date on that).

3. Are the database entries for the attachment in civicrm_file and civicrm_entity_file correct? (Compare to other files you can see.)

4. Is the file physically there in sites/default/files/civicrm (might be in a subfolder - "custom" or something).

5. Any errors in sites/default/files/civicrm/ConfigAndLog or the web server log?

[Upperholme]

Thanks for the tips - I'll work through this and report back.

[Upperholme]

Answers:

1. Does it work with a regular activity, e.g. a create a meeting and attach a file.

Yes, I can create or edit a default activity, add a file attachment and can see the hyperlinked file name in the activity view pop-up (as an aside the optional descriptive text is not visible in this pop-up, but is visible on the activity edit page). Same is true for adding a file attachment to my custom activity type.

2. Are the directory entries correct, on the admin screen under system settings - directories and in civicrm.settings.php and in the database in civicrm_settings (I'm actually not sure where the definitive place is in 4.4 - I haven't kept up to date on that).

From the civicrm.settings.php file and the db, files should be stored in sites/default/files/civicrm/custom. This is indeed where uploaded files are being stored.

3. Are the database entries for the attachment in civicrm_file and civicrm_entity_file correct? (Compare to other files you can see.)

Everything looks to be fine. I can't see any unexpected differences (other than the file naming difference noted below) between files uploaded using the file attachment functionality in an activity and files uploaded via the webform.

4. Is the file physically there in sites/default/files/civicrm (might be in a subfolder - "custom" or something).

Yes. However when viewing the files in that directory, I can see that the files uploaded via the activity field attachment have been renamed - they have file names of the form 'originalfilename-_397103ec47cd05cf0db9966819cfde14.pdf' whereas files uploaded via the webform have not been renamed.


5. Any errors in sites/default/files/civicrm/ConfigAndLog or the web server log?

Can't see anything in the CiviCRM log that looks relevant. Likewise the web server logs aren;t offering any useful clues.

Thanks for your help with this.

A little more: I also uploaded a file using the custom field, but via the CivicRM, activity edit page rather than through the webform, thinking perhaps that the issue might be down to the webform and its integration. The file uploaded fine, and was not visible in the activity view pop-up, but was visible on the activity edit page. The uploaded file had its filename changed, unlike files uploaded via the webform. Based on this evidence I'd say the issue was with the custom file upload field?