Skip Menu |

This queue is for tickets about the Sailthru-Client CPAN distribution.

Report information
The Basics
Id: 98554
Status: resolved
Priority: 0/
Queue: Sailthru-Client

People
Owner: SAILTHRU [...] cpan.org
Requestors: doug.rubino [...] powerinbox.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: {{email}} tag does not always work
Date: Tue, 2 Sep 2014 13:53:53 -0400
To: bug-Sailthru-Client [...] rt.cpan.org
From: Doug Rubino <doug.rubino [...] powerinbox.com>
Hello, The attached document contains a snippet of html that is sent through SailThru. I included the entire file, but the bug has to do with the anchor tags with image tags embedded in them. They look something like this: <a href="http:// ... {{email}} ..."> <img src="http:// ... {{email}} ..."> </a> I've left out extra attributes, and most of the url for clarity, but the full example can be found in the attached files, nested in the <table> element at the bottom of the snippet. In the code above, notice that both the anchor href and the image source have urls which contain the {{email}} tag. After this html is sent with SailThru, the {{email}} tag in the image source is replaced correctly with the recipient's email address. On the other hand, the {{email}} tag in the anchor href is replaced with the generic email: example@example.com. This appears to be a regression, as both tags were replaced correctly in the past. This is a critical bug, as the email address is necessary for user tracking. I'm sure other users also rely on the correctness of your personalization features. Thank you for your consideration. Best, Doug Rubino

Message body is not shown because sender requested not to inline it.

On Tue Sep 02 13:54:47 2014, doug.rubino@powerinbox.com wrote: Show quoted text
> Hello, > > The attached document contains a snippet of html that is sent through > SailThru. I included the entire file, but the bug has to do with the anchor > tags with image tags embedded in them. They look something like this: > > <a href="http:// ... {{email}} ..."> > > <img src="http:// ... {{email}} ..."> > > </a> > > I've left out extra attributes, and most of the url for clarity, but the > full example can be found in the attached files, nested in the <table> > element at the bottom of the snippet. > > In the code above, notice that both the anchor href and the image source > have urls which contain the {{email}} tag. After this html is sent with > SailThru, the {{email}} tag in the image source is replaced correctly with > the recipient's email address. On the other hand, the {{email}} tag in the > anchor href is replaced with the generic email: example@example.com. > > This appears to be a regression, as both tags were replaced correctly in > the past. > > This is a critical bug, as the email address is necessary for user > tracking. I'm sure other users also rely on the correctness of your > personalization features. > > Thank you for your consideration. > > Best, > Doug Rubino
Hi Doug, This doesn't appear to be an issue with the Perl client library. It may be an issue with our API, but it appears you are trying to test some zephyr functionality with a test send (This is where the example@example.com email address comes in). Please try sending normally, and it should resolve your issue. However, if it does not, please contact our support team at support@sailthru.com, and they can help you diagnose it and escalate any potential issues as necessary.
Resolve the ticket. Please reopen if there are still any issues.