User Details
- User Since
- Aug 19 2025, 3:45 PM (33 w, 6 d)
- Availability
- Available
- LDAP User
- Lars SG
- MediaWiki User
- LSandergreen-WMF [ Global Accounts ]
Today
criteria more specifically is segment > 200, segment != 1000, segment not null
Merged upstream, but this isn't super important for us, so we can just get it with our next upgrade.
@Ejegg There is code on the merge hook that is supposed to prevent contacts ending up with more than one email of the same type, by selecting another from the list of options. My guess is that in this case, it probably ran out of options since there are so many emails on that contact and started assigning them to location type 0. I think we could just allow them to be duplicates instead if we reach the end of the list, but not a high priority.
Fri, Apr 10
@AnnWF actually already has a patch ready, which I need to review, that will solve this exact problem.
It may be useful to also provide the personalized donor portal link here.
This is now done.
@ppenloglou For visibility, the following fields are no longer in Acoustic:
Thu, Apr 9
For Q4 maintenance window, remove all the disabled custom fields.
silverpop database updates for this and T422533: Change AF_lifetime_usd_total in Acoustic to both_funds_lifetime_usd_total
-- silverpop_export_stat ALTER TABLE silverpop_export_stat RENAME COLUMN foundation_lifetime_usd_total TO all_funds_lifetime_usd_total, DROP COLUMN foundation_last_donation_date, DROP INDEX endowment_last_donation_date, DROP COLUMN endowment_last_donation_date;
See T422164: Donor Portal: Dynamic link for 'restart your monthly/annual donation to prepopulate donation form with known gift details for implementation of country url param from smashpig original country.
Scheduled for Q4 maintenance window.
Wed, Apr 8
Implementation plan:
- Update table columns as needed and add field in Acoustic
- Initial set based on language and segment directly in Acoustic
- Set modified date on paypal or paypal_ec recurring donors to force update
Also update import mapping
This will need table updates after deployment.
Moving this to Later as it may not make sense to do, if we are eventually switching away from Acoustic, until that happens.
Tue, Apr 7
@NNgu-WMF Thanks for the update. Just FYI, we can push this (or other groups) to a group in Acoustic directly from CiviCRM now. There is a bit of work needing to make it clear the contact list automatically for repeated pushing, but we can handle that manually for now if this is needed.