As far as the extra text goes, that's still totally an option. I just wanted to get something functional out as a first step.

good catch on that linebreak @MSuijkerbuijk_WMF . I've got a small style change that should fix it.

Next thing to do: make snooze date visible in contact summary screen

@MSuijkerbuijk_WMF @AKanji-WMF we've got an MVP of this deployed. It's available by clicking on the Email preferences links on the Civi contact summary (that link may be down near the bottom of the right side now, not sure why).

We have switched over the production IPNs to JSON!

Moving to current sprint as @Eileenmcnaughton is incidentally solving this with her other refactors

OK, got another small patch up for the python PayPal audit. That's all I can think of for now!

In T358914#9775326, @Ejegg wrote:

Other things we'll need: import frequency_unit in queue consumer, read it out of logs in audit processor, determine frequency_unit in IPNs.

Other things we'll need: import frequency_unit in queue consumer, read it out of logs in audit processor, determine frequency_unit in IPNs.

In T358914#9764608, @Ejegg wrote:

Other work to do: Support annual donations in PayPal EC, update our logic that cancels active recurrings with no payments in 90 days, to exclude annual donations.

Patch is up for the SmashPig side of annual donations in PayPal EC, and it looks like our CancelInactives logic is already limiting to just monthly donations.

@bsisolak we should figure out what else we need to change on the Civi side to accommodate that change. I guess we can stop deduping by email address in the nightly exports? That will be a big change as we have email as the primary key in many tables we use to transform for exports, but the SQL will probably be a lot cleaner.

There's another class of failmail coming in, e.g. contacts 730314 and 180366:

Other work to do: Support annual donations in PayPal EC, update our logic that cancels active recurrings with no payments in 90 days, to exclude annual donations.

Civi already supports annual (or quarterly) donations via the frequency_unit (deafult 'month') and frequency_interval (default 1) columns on the civicrm_contribution_recur table. I'd suggest we use those same names as the query string parameters. I'll start with a patch to send those through to Civi from payments forms.

@MSuijkerbuijk_WMF and @AKanji-WMF for an initial version, I'm thinking of deciding the questions this way to simplify things:

In T351325#9757248, @Pcoombe wrote:

@Ejegg There is some special-casing on payments forms which changes the logo and some of the link targets when utm_medium=endowment. Can you make that work with wmf_medium=endowment too?

Suggested tech fix: give IPN job runner a map of email address => contact_id for special cases like this one, and when the IPN's email is on the list have the runner blank the name fields and just assign the contact_id on the message it sends to the donations queue.

@EMartin they also have an organization record, cid 3729480. Would it be better to add some logic to make sure all donations with that email go to the org record?

@MSuijkerbuijk_WMF and @AKanji-WMF : sorry, this might not actually need a change!

Some questions to clarify the desired functionality:

In T358878#9596774, @AnnWF wrote:

From slack, we need to make unsubscribe success message is not confusing for this 90 days snooze donor: sorry to see you go, you're unsubscribed OR thanks for updating your preferences, you will not receive emails to this address for 90 days.

Hah, now it's got country but I'm seeing a missing payments_final_status

In T362087#9740701, @MSuijkerbuijk_WMF wrote:

@Ejegg Thanks for explaining. Just a follow up questions:

• Is the 'Recurring Upgrade Declined' a criteria in Acoustic? I don't remember if we added it already.

• Does it have an expiration period? I'm asking because we need to leave a window with the Declined on, but then after (for example) +12 months, reintroduce them. Is this how this criteria works?

Thanks

In T362087#9707794, @krobinson wrote:

@Ejegg this is great!

Can I confirm a couple of things:

• Can we use that for other donors with other CIDs, so that if a donor just emails us saying never monthly etc, we can mark their record? Or is it only for those who have received the email and thus already have their record marked in some way?

@krobinson You can add the 'Recurring Upgrade Declined' activity to any contact and it will act as an opt-out to future recurring upgrade emails - it's not dependent on having already gotten one.

In T362087#9711941, @MSuijkerbuijk_WMF wrote:

Thanks @Ejegg -- what do you mean with exclude all donors when they have 'Update recurring contribution'? Do you mean all those who receive the email?
We do not want to do that. Many donors did not open, but that doesn't mean we don't want to reach them again with an upgrade ask and be successful.

@MSuijkerbuijk_WMF when Donor Relations manually edits a recurring contribution, e.g. for a donor that emailed them instead of clicking a link in the email, the donor's record gets an activity of type 'Update recurring contribution'. The vast majority of the people who got the email will NOT get an activity of this type.

The associated patch is merged. Is there more to review?

I've just deployed a change to make it possible to manually record a 'Recurring Upgrade Decline' activity against a contact record, for donors who receive the email asking them to upgrade their recurring, but who reach out to DR instead of clicking the 'no' button. Adding this activity will exclude them from future mailings.

I think it should accept them ever since this commit: https://phabricator.wikimedia.org/rWFSP3dee4c1549a8c4e6cfc760cb7a3f63d4ef1dad1a

Thanks @Pcoombe . Creating a custom skin sounds fun, and the faster load times might give a nice boost for donations!

• How is the checksum column populated for contacts? Could something have gone wrong there?

@Pcoombe brought up in a meeting that we need to update the parameters we pass through to the Thank You pages. To avoid really long URLs, he suggests we do a hard cutover in the payments-wiki code. This means he will need to update the TY page javascript to accept both prefixes for a while.

Hi @AMJohnson I can't seem to sign in to Zendesk either via Okta or with my old password, and the reset password link doesn't send me anything. Are you able to reactivate agent accounts?