The 'simplenews' token [simplenews-receiver-name] resolves into the recipient's user name (unless the subscriber is an anonymous user). This does not look well when the user name is different to her real name. To make a perfect personalised newsletter mail, a new token such as [simplenews-receiver-realname] would be required which instead resolves into the recipient's real name.

CommentFileSizeAuthor
#1 simplenews-6.x-2.x_simplenews-receiver-realname.668550.patch1.95 KBroball

Comments

roball’s picture

roball commented
Status: Active » Needs review
StatusFileSize
new simplenews-6.x-2.x_simplenews-receiver-realname.668550.patch1.95 KB

The attached patch solves this issue. Works fine for me!

sutharsan’s picture

sutharsan commented
Status: Needs review » Closed (won't fix)

I have stated before that I will only accept a flexible solution for both anonymous and authenticated users. This patch is a limited solution but does not bring us closer to a grand solution.

roball’s picture

roball commented
Title: New token [simplenews-receiver-realname] » Personalized mails (one approach: token [simplenews-receiver-realname])
Status: Closed (won't fix) » Active

Can we please discuss this issue further? I think it is very important being able to send out personalized mails. What about exposing the "$account" variable as the object of the recipient user to "simplenews-newsletter-body--[NID].tpl.php" - similar than the existing $node variable? Then we would have great flexibility, and could use something like this:

if (!empty($account->name)) {
  $salutation = '[simplenews-receiver-name]';
} else {
  $salutation = 'friend of our organisation';
}
print 'Dear ' . $salutation;
sgabe’s picture

sgabe commented

See the Simplenews RealName module.

sgabe’s picture

sgabe commented
Status: Active » Fixed

See my previous post.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.