Project:Personalized E-mails
Version:6.x-1.x-dev
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:postponed (maintainer needs more info)

Issue Summary

Are there plans to make port?

Comments

#1

I'd find this helpful as well. Maybe there's already an equivalent module / functionality?

#2

+1

#3

Status:active» needs review

Hi everyone,

This is my first attempt at porting. I'm still learning PHP, so please keep in mind when testing (this is actually the first attempt at PHP as well). I haven't tested with a live site yet. This looked easy enough to cut my teeth on.

This uses user profiles (admin/user/profile) as an optional extra.

Have included the whole package. I haven't updated the readme.

Have fun,

TJ

AttachmentSize
pmail.zip 10.8 KB

#4

Status:needs review» needs work

The personalised email package I posted before needs work.

Just tried it on a live site.

Emails would not send.

I don't have the time right now to look at it.

#5

Status:needs work» needs review

Stonjie's port to Drupal 6 fixed.

AttachmentSize
pmail.zip 10.87 KB

#6

Did any one tried this? does it work for 6.10?

#7

It appears to set the From: address correctly but does not pick up from the profile anything other than [user]. If for example, I change that to: [profile_firstname], that setting is ignored.

#8

The [profile] tokens are not properly substituted when you create an Action/Trigger either.

#9

Suggestion - can this be committed as a 6.x-dev branch with the known issue regarding tokens? Perhaps that will be a start to finishing the updates to the code. Thanks.

#10

subscribe

#11

Looks like the 6.x port was committed to a new branch today. Awesome!

#12

Anything going with this or is this module no longer being maintained?

#13

Version:5.x-1.x-dev» 6.x-1.x-dev

interested in benefits of this module
subscribing

#14

Title:Drupal 6» Drupal 6 stable release
Status:needs review» active

#15

Category:feature request» task
Status:active» postponed (maintainer needs more info)

Roadmap for a stable release:

  • Test with Token Profile instead of included patched token.user.inc.
  • Also test with latest patch from #125640: Profile tokens, since this shall replace Token Profile in the future.
  • If successful remove patched token.user.inc.

#16

subscribing

#17

+1

I wonder if I should wait for the release? Or should I use 'as is'?

Do I need 'Token Profile', "Content Profile', token.user.inc patch?

With the patch if token.module is updated - what do I do?

nobody click here