I've like to override the content produced by the following token in the default digest template

[subs:items:index:#0:formatted]

This is the default text output of this token:

| Author: Anonymous
| Title: Wave of UK walkouts shocks the bosses
 

| LINK: https://ibew177.org/content/wave-uk-walkouts-shocks-bosses
| ---------------------------------------------------
| Direct unsubscribe link (thread):
| https://ibew177.org/s/del/...

I'd like to simplify it to the following:

Title: Wave of UK walkouts shocks the bosses
https://ibew177.org/content/wave-uk-walkouts-shocks-bosses

Basically I'm trying to show only the node title and the node link.

I tried using [node:title] but that didn't work.

Can someone help me? I feel like I'm missing something obvious here.

CommentFileSizeAuthor
#6 index_in_repeat_loop.png14.02 KBsalvis

Comments

salvis’s picture

Status: Active » Fixed

You can use [subs:items:index:#0:as-node:title], or you can change the template that's being used for generating the item.

Status: Fixed » Closed (fixed)

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

nicolash’s picture

Is there somewhere where these particular Subscriptions tokens are listed?

salvis’s picture

Status: Closed (fixed) » Active

Yes, they appear right on the create/edit template page, if you install the Token module. Maybe we do not sufficiently recommend the Token module?

The #0 is explained under "{{count#repeated_text}}" in the Dynamic Text Information fieldset on the same page.

nicolash’s picture

Thanks salvis. I only made the connection of subscriptions tokens with regular tokens via the example you gave in #1...[subs:items:index:#0:as-node:title]. Looking at the template edit page again, I can't find where that is explained, but there's a fair bit of info and I may well be missing it.

salvis’s picture

StatusFileSize
new14.02 KB

"Repeat" syntax explained

Are we not looking at the same thing?

salvis’s picture

Status: Active » Fixed

No follow-up.

Status: Fixed » Closed (fixed)

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