Skip to main content
Craft CMS

Return to Answer

replaced http://craftcms.stackexchange.com/ with https://craftcms.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

The first part of the answer in the post you linked toanswer in the post you linked to is wrong in the context of the Contact Form plugin.

Craft only takes the custom "HTML Template Path" email setting into account when EmailService's sendEmailByKey is called, which is used for pre-defined Craft emails.

The Contact Form uses EmailService's sendEmail, which won't take it into account.

It hasn't been released as part of an official Contact Form plugin release yet so there's no documentation, but thanks to this pull request, you've got an onBeforeMessageCompile event that will give a plugin a chance to modify the contents of the email.

The first part of the answer in the post you linked to is wrong in the context of the Contact Form plugin.

Craft only takes the custom "HTML Template Path" email setting into account when EmailService's sendEmailByKey is called, which is used for pre-defined Craft emails.

The Contact Form uses EmailService's sendEmail, which won't take it into account.

It hasn't been released as part of an official Contact Form plugin release yet so there's no documentation, but thanks to this pull request, you've got an onBeforeMessageCompile event that will give a plugin a chance to modify the contents of the email.

The first part of the answer in the post you linked to is wrong in the context of the Contact Form plugin.

Craft only takes the custom "HTML Template Path" email setting into account when EmailService's sendEmailByKey is called, which is used for pre-defined Craft emails.

The Contact Form uses EmailService's sendEmail, which won't take it into account.

It hasn't been released as part of an official Contact Form plugin release yet so there's no documentation, but thanks to this pull request, you've got an onBeforeMessageCompile event that will give a plugin a chance to modify the contents of the email.

Source Link
Brad Bell ♦
Brad Bell ♦
  • 67.6k
  • 6
  • 75
  • 145

The first part of the answer in the post you linked to is wrong in the context of the Contact Form plugin.

Craft only takes the custom "HTML Template Path" email setting into account when EmailService's sendEmailByKey is called, which is used for pre-defined Craft emails.

The Contact Form uses EmailService's sendEmail, which won't take it into account.

It hasn't been released as part of an official Contact Form plugin release yet so there's no documentation, but thanks to this pull request, you've got an onBeforeMessageCompile event that will give a plugin a chance to modify the contents of the email.