Personalizing newsletters

+1 on this. A few more variables shouldn't conflict with the 'simpleness' of the module, and will make the communication that much more effective.

I needed this functionality for an accounting system we're developing on Drupal.

The attached patch basically allows to insert user profile fields into newsletters. However, these tokens should be used carefully as you do not know which profile fields a user has filled in and because there is no profile information for anonymous recipients (without a user account) at all. I'm currently unsure how to handle those conditions. It might be that there are only limited solutions to this issue, such as (optionally) sending a newsletter to recipients that have filled in the required fields.

Anyhow, IMHO this approach should be converted into a new hook_simplenews_fields(), so any module is able to provide additional (text replacement) fields for newsletters. F.e. you can think of amount of unread private messages, time since last login, birthday reminders, etc.

what about utilizing the token module instead of reinventing the wheel?

read more about its features at http://drupal.org/project/token

Token module currently does not support profile fields. However, smk-ka is already working on this implementation over here.

I'm also interested in personalizing newsletters. Make profile fields available is a good idea. But I only need 'username' to write "Hello username" in a newletter, so I used user-token to get this.

[reg-since] and [log-since] only show years and weeks, so I didn't insert them in the description.

To get the send-variable in simplenews_view() I used $_POST, because it was the only way I found.

I inserted token_replace() in simplenews_mail_send(), as in simplenews.module_5.patch - perhaps there is a better place.

Can anybody have a look at the code. I don't know how to make it better.

I implemented the Token module patch for profiles, but it did not seem to fully meet my needs.

Then I tried the above patches in #3 and #7 together to cover all conditions. These definitely seem to work.

What's the possibility of getting #3 and #7 rolled into the next version of Simplenews, or are there other plans for Token which will meet these needs? If it makes sense to get them into Simplenews, I've created an updated patch. It is attached and has been tested with 5.x-1.5.

Hi,

All of the above patches failed to apply to the current stable release.
With the patches from #3 and #7 one hunk failed.
The patch in #8 didn't work at all, because it was malformed.

Please look into this again.
In the meantime I'll try and check what went wrong. If it works, I'll post a new diff.

Raoul

[edit] Patched it (#8) manually, against 5.x-1.5, tested, and it seems to work. Please see the Diff attached and review. Thanks.[/edit]

[edit 2] Actually, the profile fields don't work, whether I'm using the @profile_name or %profile_name variable. The tokens work perfectly though. I need to review my patch.[/edit]

Patching manually using #8 should work with no problem, including the profile options. I've got it running on a live production site right now.

Also see http://drupal.org/node/127178 for similar request.

@callison: This issue is about token integration, i.e. using personal data not about collecting it.

Subscribing

Duplicate of #183120: Support Token module. Changing version to HEAD.
Where possible code of these patches will be used for HEAD.

Some quick solution here: http://drupal.org/node/183120#comment-1398060

Try Views Send. It allows personalization and full recipient list filtering based on Views.