You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#211 started sending emails to companies regularly, asking them to update their pledges. If they don't have any confirmed contributors, it mentions that they'll be deactivated. The 5ftf_inactive_deactivate_date meta field was added to indicate when they can be deactivated.
In this issue, we should:
add a cron job to remove contributor posts that have 0 hours, so that the count of confirmed contributors on pledges will be accurate. That could maybe tie into update_all_cached_pledge_data.
add a cron job to pull all companies that have 5ftf_inactive_deactivate_date < now(). If they still don't have any confirmed contributors, we should deactivate them. If they have added contributors, then we can delete the 5ftf_inactive_deactivate_date field.
send companies a final email notice that their pledge is deactivated, with a note on how to reactivate their pledge
send contributors a final email, similar to above. avoid sending send_contributor_removed_email()
The text was updated successfully, but these errors were encountered:
@iandunn As part of this, can contributors and companies get a final email notice that their pledge is deactivated, with a note on how to reactivate their pledge?
#211 started sending emails to companies regularly, asking them to update their pledges. If they don't have any confirmed contributors, it mentions that they'll be deactivated. The
5ftf_inactive_deactivate_date
meta field was added to indicate when they can be deactivated.In this issue, we should:
update_all_cached_pledge_data
.5ftf_inactive_deactivate_date < now()
. If they still don't have any confirmed contributors, we should deactivate them. If they have added contributors, then we can delete the5ftf_inactive_deactivate_date
field.send_contributor_removed_email()
The text was updated successfully, but these errors were encountered: