Opened on 12/22/2017 at 08:17:01 AM
Closed on 01/31/2018 at 04:52:01 PM
Last modified on 01/31/2018 at 04:52:27 PM
#6215 closed change (rejected)
Create custom email template for ABP Newsletter
| Reported by: | ire | Assignee: | |
|---|---|---|---|
| Priority: | P2 | Milestone: | |
| Module: | Websites | Keywords: | |
| Cc: | jeen, juliandoucette, wspee | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by ire)
Background
In #6210 we are implementing a custom Backclick template for the ABP Newsletter (See Specification).
After users sign up using the form, they receive 2 emails:
- An email asking for their confirmation
- An email confirming their successful signup to the newsletter
The default Backlcick template isn't appropriate (see screenshot).
What to change
Design and implement a custom newsletter template.
Attachments (4)
Change History (19)
Changed on 12/22/2017 at 08:17:20 AM by ire
Changed on 12/22/2017 at 08:17:32 AM by ire
Changed on 12/22/2017 at 08:17:59 AM by ire
comment:1 Changed on 12/22/2017 at 11:51:53 AM by juliandoucette
- Owner set to juliandoucette
comment:2 Changed on 12/22/2017 at 01:13:35 PM by juliandoucette
- Owner juliandoucette deleted
Changed on 12/22/2017 at 04:05:48 PM by juliandoucette
comment:3 Changed on 12/22/2017 at 04:31:07 PM by juliandoucette
comment:4 Changed on 12/22/2017 at 04:31:48 PM by juliandoucette
- Priority changed from P2 to P5
- Ready unset
comment:5 Changed on 12/22/2017 at 04:54:58 PM by juliandoucette
- Priority changed from P5 to P2
comment:6 Changed on 01/03/2018 at 02:09:47 PM by ire
Resource for developing HTML email - https://github.com/leemunroe/grunt-email-workflow
comment:7 follow-up: ↓ 9 Changed on 01/03/2018 at 04:15:11 PM by jeen
Created a spec specifically for the email confirmation [on GitLab #118](https://gitlab.com/eyeo/spec/merge_requests/118).
comment:9 in reply to: ↑ 7 Changed on 01/04/2018 at 07:17:11 AM by ire
Replying to jeen:
Created a spec specifically for the email confirmation [on GitLab #118](https://gitlab.com/eyeo/spec/merge_requests/118).
Thanks Jeen! We also need the email content for the final email sent after the user's subscription has been confirmed.
comment:10 follow-up: ↓ 11 Changed on 01/04/2018 at 10:13:29 AM by jeen
I don't think it is necessary to have another email confirming the user's subscription? Usually, the message in the redirect page is enough? Otherwise, it is simply cluttering up their inbox with unnecessary mail.
comment:11 in reply to: ↑ 10 Changed on 01/05/2018 at 09:27:05 AM by ire
Replying to jeen:
I don't think it is necessary to have another email confirming the user's subscription? Usually, the message in the redirect page is enough? Otherwise, it is simply cluttering up their inbox with unnecessary mail.
Okay. I'll look into how to disable the final email. Thanks!
comment:12 Changed on 01/10/2018 at 01:18:12 PM by ire
- Owner set to ire
comment:13 Changed on 01/26/2018 at 11:27:26 AM by ire
- Owner ire deleted
comment:14 Changed on 01/31/2018 at 04:52:01 PM by ire
- Resolution set to rejected
- Status changed from new to closed
comment:15 Changed on 01/31/2018 at 04:52:27 PM by ire
Closed on Gitlab https://gitlab.com/eyeo/web.adblockplus.org/issues/1
I have attached extra.html which contains the HTML that was discovered inside the Backclick signup form template. This HTML seems to contain two pages responsible for email confirmation.
We no longer use trac for design requests or product specification. Instead, we send design requests to product@eyeo.com and specify products in gitlab. As a result, I think we should repurpose this ticket to implement the specification of these pages when they are created.
@jeen, @wspee will you please see that this makes it's way into your processes appropriately.
It's hard for me to comment on what's missing because I can't read the pages. But it seems: