-
Notifications
You must be signed in to change notification settings - Fork 10
Conversation
Squashed. |
I'm wondering if we need the activation thing to be so complex, and whether we need them to hang around. I'm thinking perhaps all we need is for a row to be created when a change is requested, and to be considered active if it's been less than |
Will simplify the activation thing as suggested. |
@pmclanahan Updated the activation logic, but spotted some other problems. Updated the pull request description with the latest status. |
@@ -183,7 +184,7 @@ The following URLs are available (assuming "/news" is app url): | |||
Returns information about all of the available newsletters:: | |||
|
|||
method: GET | |||
fiends: *none* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol
This is currently blocked because ET won't let us send a triggered email to an address that's not already in our data at ET (as best i can tell, see this bug comment). Waiting for jdavis to respond. |
Could this pull be closed if it's not going to be needed? I'm trying to neaten my GitHub open issues and pulls. |
Sure. Also, hi Dan 👋 |
Ready to review, but not to merge. The triggered email sends don't work for brand new email addresses (that aren't in ET yet), and the confirmation messages in ET are just placeholders, not the final text.