EEC.MS - ExpressionEngine add-ons
You are here: Home → Forum Home → Extensions → MX Notify Control → Thread
Can’t get channel:entries tags to display
Hello,
My notification template will only display the title of the entry added, nothing else, not the entry_id or any custom fields. For entry_id it displays “0”.
When I add a channel:entries tag it does process it somewhat, in that it displays something for every entry it finds, but not any actual values.
We have quite a few add-ons running and I’m wondering if any of them might be conflicting with MX Notify, but am concerned about disabling them for fear of losing their associated data.
Any ideas?
could you please give me more information - EE version, NC version, Trigger?
Hi,
Thanks for quick response. EE v2.2.2 build 20110801, NC v2.2.6, trigger Entry Added.
My template is:
A job application / event registration has been submitted:
{exp:channel:entries
entry_id="{entry_id}"
dynamic="off"
status="not closed"
disable="categories|pagination|trackbacks"
}
{entry_id}, {title}
{/exp:channel:entries}
The text-only output I receive by email is:
A job application / event registration has been submitted:
0, adam@adamkhan.net @ EXETER: Practical Localism – how to sustain
investment and manage economies (17 Jan 2012)
0, adam@adamkhan.net @ EXETER: Practical Localism – how to sustain
investment and manage economies (17 Jan 2012)
0, adam@adamkhan.net @ EXETER: Practical Localism – how to sustain
investment and manage economies (17 Jan 2012)
0, adam@adamkhan.net @ EXETER: Practical Localism – how to sustain
investment and manage economies (17 Jan 2012)
0, adam@adamkhan.net @ EXETER: Practical Localism – how to sustain
investment and manage economies (17 Jan 2012)
Etc (based on number of entries it finds}
“adam@adamkhan.net @ EXETER: Practical Localism – how to sustain investment and manage economies (17 Jan 2012)” is the title of my entry, so it’s getting that.
ok. It is my bug. I will publish update in 2 hours.
done. version 2.2.7
Hi Max, thanks for the quick turnaround! It’s not quite there but good enough for my purposes.
One problem I see is that the {title} variable is always the title of the entry submitted, even though sometimes we don’t want it to be (eg, if it’s the title of a related entry). My workaround for this is to use the query module and create an alias for the title.
Another problem is that tags within tags don’t work, eg, Playa fields. My workaround here is to call Playa from outside the channel:entries tag.
Thanks again,
-Adam
it’s my interface mistakes. Possible I need to add some prefix ({nc_title} for example) for all variables which entered with NC to prevent it. Thanks for report. And I will check Playa filed too.