I can't include some files with the emails that are sent. I know that the default template are including the code to do it. At first I thought that it was cause my files are private so I tried with a different content type which is public but no dice.

{{!![subs:files:field_myfile:count]#| Attached files:
{{[subs:files:field_myfile:count]#| [subs:files:field_myfile:index:#0:url]
}}}}

Nothing is displayed. Do I need to change something else ? Is there a way to include the file as attachements instead of a link in the mail ?

Comments

dmegatool’s picture

dmegatool commented
Component: subscriptions_cck » User interface
salvis’s picture

salvis
he/his
commented

I suspect that 'field_myfile' is not the name of your files field.

dmegatool’s picture

dmegatool commented

As if I didn't check that ;-)

For some reason it didn't worked on my dev setup but it's working on the live. Weird cause it's on the same server and all. Guess there's something wrong in my dev configuration :/

Thx for the reply.

dmegatool’s picture

dmegatool commented
Status: Active » Closed (cannot reproduce)
jerry’s picture

jerry commented
Version: 7.x-1.0 » 7.x-1.1
Status: Closed (cannot reproduce) » Active

Re-opening this issue because I'm having what seems to be the same problem.

I added a file field (named "field_files", as that's the default in the mail template) to both forum topics and their comments, but the expected file list didn't appear in subsequent Subscriptions E-mail. That part of the template was unchanged, and the fields displayed properly when rendered by the site, but the template tokens weren't working as expected.

A bit of digging around revealed that the files tokens weren't actually added to comment or node templates unless the 'view uploaded files' permission was granted. As that's a D6 core upload.module permission (if I remember correctly), this guaranteed that it would fail with D7 fields. Commenting-out that check (at lines 61 and 103 of file subscriptions_content.tokens.inc) allowed the files tokens to work as expected. I'm not sure if there's a more appropriate check that should be employed instead.

salvis’s picture

salvis
he/his
commented
Component: User interface » Code
Category: support » bug
Status: Active » Fixed

Whoa, this very minute I came to the same conclusion based on feedback from Nigristriata in #1825302: empty tokens when sending out notifications - it depends on who is the recipient.

Thank you for the analysis. We can just remove those checks. Core's file.module takes care of checking access based on whether any containing entity is accessible, which is sufficient here (we don't send inaccessible entities).

The site that I used for testing that feature was actually upgraded from D6 and the users still have the 'view uploaded files' permission, so it worked just fine!

I've just pushed the fix to the -dev version (give it up to 12h to be repackaged).

Status: Fixed » Closed (fixed)

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