Good afternoon,

I added in the "Send an HTML mail to a user" action to a rule, then filled in all fields in the form and saved. When I went back to edit the HTML message, it was gone. All other fields saved correctly. I tried all input formats, including disabling rich text, but the "HTML message" field would not save. I am using CKEditor with the WYSIWYG plugin, and am on Drupal 6.19.

Has anyone else had this issue, or am I missing something really simple here :)?

Thanks very much,
Ben

CommentFileSizeAuthor
#7 mimemail_1181486_02.patch718 bytessgabe
#1 mimemail_1181486_01.patch2.52 KBsgabe
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sgabe’s picture

Component: User interface » Code
Status: Active » Needs review
FileSize
2.52 KB

Can you test the attached patch?

bnthms88’s picture

This works great! The "Send an HTML mail to a user" action now saves correctly. Thanks very much!

sgabe’s picture

Status: Needs review » Fixed

Committed to the development snapshot.

bakr’s picture

Dear Gabor,

I have the same issue as above, though using the latest dev snapshot for 6.x

sgabe’s picture

I couldn't reproduce this with the development snapshot. Did you emptied the cache?

Are you using the "Send an HTML mail to a user" action?

bakr’s picture

Thanks for quick reply, I am using "send to all users of role"

sgabe’s picture

FileSize
718 bytes

Ahh...the submit function is missing for that action.

bakr’s picture

You are fantastic .. you really make my day.

I was fiddling with Action Email role module, but it lags the html support at the time being.
Though it has a great feature of picking tokens into writing text field.

Keep up the good work.

Best Regards
Bakr

sgabe’s picture

Priority: Normal » Major

Changing priority since this bug makes Rules actions unusable. However the patch is committed to the development snapshot.

bakr’s picture

Scenario:

* I have created a new Role called "Dummy"
* have enrolled my self to that role. .. (The purpose is to direct email to users under this role, to avoid nagging other people with my test emails)
* have created a simple rule by which an email is triggered "send to all users of role" upon creation of any node in my drupal.

The problem is:
* After filling a new form, and submitting, I get a white screen 'of death', with no more clue what is happening.

Notes:
* I am using todays latest dev release
* when deleted and recreated the rule, the issue persists
* when i disable the rule, the issue diappers, and my node saves normally without and problem.

Clearly some php error is lurking somewhere.

Best Regards..

bakr’s picture

Title: HTML Message not saving in Rules Action form » White Screen when triggering the mimemail action: "send to all users of role"

Yesterday(when things were working) I noticed that outlooks strips the inline css styling from the html message body

I am trying so sort out the HTML styles to be consistant once viewed from within outlook 2007 client.

I am using inline css style to format my html table content in the email body.

What is the best way to get around this and preserve the css stylings?

bakr’s picture

Status: Fixed » Needs review
bakr’s picture

I have disabled the mimemail module, and tried "mailsystem+autoload+html mail" the issue still exists,

So far I was using drupal email sybsystem,
now I will test with smtp library "PHPMailer"

sgabe’s picture

Title: White Screen when triggering the mimemail action: "send to all users of role" » HTML Message not saving in Rules Action form
Status: Needs review » Fixed

Please don't change fixed issues, but open a new one. What you are experiencing is totally different. Please check the Issue queue handbook.

FYI Mime Mail doesn't compatible with Mail System and HTML Mail on Drupal 6.x!

bakr’s picture

Thanks Gabor for the guide, I am getting the etiquette ;)

I am opening a new thread #1188916: Drupal Mailing Solutions in Exchange Server 2010 Vicinity to extend discussion on that issue and share findings.

dkingofpa’s picture

Just a warning to others, the patch in #7 is not the latest version that fixes the OP issue. It's just another patch that can be applied after the actual patch in #1.

Status: Fixed » Closed (fixed)

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