Populate user info, when sending membership expiration e-mails

Components

Labels

Description

Plan

  1. replace the "<inp2:u_" in the subject and body of both e-mails with "<inp2:" (to use externally provided prefix)

  2. from the "u:OnCheckExpiredMembership" event ("membership_expiration" scheduled task) load the user object (for user, whose membership is affected) before sending the actual e-mail

Context Information

None

Additional information (do not use)

None

Activity

Show:

[API] Administrator January 23, 2016 at 6:03 PM

User committed a fix to 5.3.x. Commit Message:

Fixes - Populate user info, when sending membership expiration e-mails

Differential Revision: http://qa.in-portal.org/D179

Alex January 23, 2016 at 6:03 PM

alex closed D179: - Populate user info, when sending membership expiration e-mails by committing rINP16319: Fixes - Populate user info, when sending membership expiration e-mails.
alex updated the diff for D179: - Populate user info, when sending membership expiration e-mails.

Gleb Sinkovskiy December 24, 2015 at 9:27 AM

glebs accepted D179: - Populate user info, when sending membership expiration e-mails.
D179: - Populate user info, when sending membership expiration e-mails is now accepted and ready to land.

http://qa.in-portal.org/D179

Alex December 6, 2015 at 2:36 PM

alex added a dependent revision for D179: - Populate user info, when sending membership expiration e-mails: D180: - Do not use "Web Request" and "Session" concepts in CLI.

http://qa.in-portal.org/D179

Alex December 6, 2015 at 1:45 PM

alex updated the diff for D179: - Populate user info, when sending membership expiration e-mails.
alex added a comment to D179: - Populate user info, when sending membership expiration e-mails.

Forgot to add language pack changes

http://qa.in-portal.org/D179

Fixed

Details

Priority

Assignee

Reporter

Developer

Reviewer

Change Log Group

Fixed

Change Log Message

Patch Instructions

Patches must be submitted through Phabricator.

Story Points

Fix versions

Created December 6, 2015 at 11:25 AM
Updated December 29, 2024 at 8:54 PM
Resolved January 23, 2016 at 6:59 PM