Project:Reroute Email
Version:5.x-1.0
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Are there any plans to update this module to Drupal 6?

Comments

#1

This is indeed a frequently asked question.

#2

Status:active» needs review

As I need this module I did a port to Drupal 6. I have attached following files:

reroute_email-6.x-1.x-dev.tar_.gz is a modification of the Drupal 5 branch of the module for testing purposes. To test the D6 port just download this archive file, unpack it in your site's module folder and activate it. It will appear as revision 6.x-1.x-dev.

reroute_email-277525-2.patch provides the same port as an "official" patch file (following the standardized naming convention as described at http://drupal.org/patch/submit) which applies against the Drupal 5 cvs branch (branch tag DRUPAL-5) of the module.

@kbahey: if you accept this patch I would be glad if you would provide an official 6.x release of the module.

AttachmentSizeStatusTest resultOperations
reroute_email-6.x-1.x-dev.tar_.gz7.49 KBIgnored: Check issue status.NoneNone
reroute_email-277525-2.patch3.08 KBIgnored: Check issue status.NoneNone

#3

Status:needs review» postponed (maintainer needs more info)

Thanks for the patch.

There should be a 6.x dev release tomorrow here http://drupal.org/node/286739.

I am wondering why you use:

$msg[] = ...
$msg[] = ...

Instead of:

$msg = ...
$msg .= ...

#4

Title:Drupal 6» Port reroute_mail to Drupal 6

Changing title.

#5

Thank you for providing the 6.x dev release.

I had to use $msg[] because $message['body'] is an array in Drupal 6 (see the description of $message array in the Drupal 6 API function hook_mail(). I noticed this when I started debugging the ported code.

#6

Status:postponed (maintainer needs more info)» fixed

OK.

I created a stable release.

Thanks for your contribution.

#7

Status:fixed» closed (fixed)

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

nobody click here