Timeline for Sending email forms using Postmaster - missing some key info on parsing fields
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2013 at 22:23 | comment | added | foamcow | The new version you sent to me and the help you gave me here has sorted the problem. Many thanks. | |
| Oct 29, 2013 at 22:23 | vote | accept | foamcow | ||
| Oct 29, 2013 at 15:09 | comment | added | Justin Kimbrell | Ok, I am going to look into this in detail today and figure out the issue. Last time I tested this stuff, it worked 100% as I built this feature directly for another user. | |
| Oct 28, 2013 at 23:41 | comment | added | foamcow | The emails are triggered but the message still contains {hook:my_field} rather than the form data. I can only get anything to send by hardcoding an email in the To email field of the hook setup - if I try to use the actual email data from the form I get a Mandrill 500 error - presumably because it's using the tag instead of an email address. | |
| Oct 28, 2013 at 23:17 | comment | added | Justin Kimbrell |
You are right. This is a parse order issue. What if you replace {count} with {entry_id}?
|
|
| Oct 28, 2013 at 22:12 | comment | added | foamcow | OK I've set it up as you suggest but still no joy. The tags in the message aren't parsed. Also, and this is weird, the {count} variable only returns "1" for each pass through the loop but if I put the entries loop OUTSIDE the postmaster tags then it works as it should and I get incremented values. | |
| Oct 28, 2013 at 20:43 | history | answered | Justin Kimbrell | CC BY-SA 3.0 |