BLOCKED - Allow for more tokens in CoreMessaging E-Mails

Description

It would be extremly helpful to have more tokens availble in EMAIL_MESSAGING_DISPATCH_BODY at GlobalResources.resx. Currently the MessaginScheduler is only capable to create links to the core accounts module.

If one is working with a third party module for subscriptions and / or user acocunts there is no chance making the e-mail templates match another setup.

Background: The CoreMessaging scheduler expects the core subscriptions module to be on the edit account page behind the third tab.

By adding tokens like
-[RECIPIENTUSERID]
-[RECIPIENTDISPLAYNAME]
-[RECIPIENTEMAIL]
-[RECIPIENTVANITYURL]

one has much more flexibility in creating templates that much more advanced setups. The required user object is availble anyways in that context.

I will provide a pull request for this shortly.

QA Test Plan

None

Activity

Show:
Philipp Becker
September 5, 2014, 6:32 PM

My first assumption would be that Globals.UserProfileUrl is not scheduler safe.

cathal connolly
September 6, 2014, 2:24 PM

Philipp is correct, that method has an implicit httpcontext requirement i.e.

/// <returns>Formatted url.</returns>
public static string UserProfileURL(int userId)
{
string strURL = "";
PortalSettings portalSettings = PortalController.Instance.GetCurrentPortalSettings();

strURL = NavigateURL(portalSettings.UserTabId, "", string.Format("userId={0}", userId));

return strURL;
}

The simplest solution is (obviously) to remove the UserProfileUrl part - is this acceptable, or do you require us to try to generate some method that does not require portalsettings (and an overload of navigateurl that doesn't require it)

Philipp Becker
September 6, 2014, 8:46 PM

I think one create that url by using recipientuserid. I'm happy with removing that token.

Ken Grierson
September 7, 2014, 2:40 AM

Hello Cathal;
The stack trace and pertinent information is in the linked issue https://dnntracker.atlassian.net/browse/DNN-5823

Ken Grierson
September 12, 2014, 4:43 PM

Verified in 7.3.3 clean installation and upgrade scenarios

Assignee

Unassigned

Reporter

Philipp Becker

Story Size

None

Severity

Minor

Triage

New

Fixed in Build

Dev Owner

None

Includes Code Fix

Yes

Documentation Required

No

Trouble Ticket

None

Requires More Info

None

QA Story Points

None

QA Owner

None

Injected

None

Automation Required

None

Code Review Owner

None

Components

Fix versions

Affects versions

Priority

Low
Configure