I'm working on a project that will generate a lot of email feedback to a variety of people in an organization for myriad reasons. I'd like to do more than use the symphony/template/notifcation.tpl specifically customized HTML emails.

I'm running Symphony 2.2.5 and Members 1.1.1 extension.

That being said, the two extensions, both by long-time Symphonians, that I see discussed in the forum are:

  1. Email Template Manager
  2. Email Template Filter

I would love it if a Symphony forum members would chime in on any or all of the following:

  • What are the differences between the two extensions?
  • What circumstances favor one or the other extension and why?
  • What are the Pros and Cons of the two extensions?

As always, thank you for your time and interaction. They are valuable to me and to everyone who uses the forum.

Based from this comment, but updated to reflect the current truths.

ETF provides a UI to create your filter and therefore requires no knowledge of PHP. It will send HTML emails to the recipients and has a logging functionality so you can see what emails were sent and when. The tutorial (sending different emails to different addresses depending on a particular option set on the form) is our most common use case at work. Creating your email is done using normal Symphony pages/datasources (and events if you want to). ETF recently supports sending of attachments, by looking for <link rel='attachment' href='your/attachment.pdf' /> in your HTML.

ETM is powerful in that you can customise everything, that is, plaintext copy, HTML copy, add attachments and so forth. It also offers filters so that you don't have to know your way around PHP (so essentially provides the same basic functionality as ETF). Creating your email template is done via the backend of Symphony, so is a little different to the usual workflow, but has some nice functionality in that you can ?debug pages in the backend.

The extensions almost come down to personal preference these days. ETF uses standard Symphony workflow, ETM is slightly different but gives you more power and flexibility if you need it. ETM probably has the upper hand in that's it's more actively developed, but both have been stable in my experience. The one con of ETM (and I could be wrong), is that it lacks logging functionality so you can see what emails were sent.

Glad to see the ETF and ETM are still in use!

As brendo said, there is little or no difference if you only look at features. Both support sending HTML and PLAIN emails, both using either an API or event filters.

In my eyes, the biggest upside of the ETM is that you will be able to use it with the new Email Newsletters extension, which will only support the ETM for its templates. So if you ever plan on sending mass-email, the ETM is the way to go.

I am running into issues with ETF and sending the Member's extension recovery code. Looks like ETM is better for the Member's extension as well.

Yes. ETM was specifically designed to work with the Members extension.

Actually, I didn't realize the Member's recovery code is the password field. So both ETM and ETF can cope. I do prefer the ETM integration though.

Thank you @Brendo, @creativedutchmen, @Lewis and @bauhouse. Your feedback is golden, exactly what we needed to know. Much appreciation.

Is Email Template Filter (ETF) still in active development or has it been deprecated in favour of Email Template Manager (ETM)? ETF doesn't look like it's been updated in a while so just wondering if it's still a viable option?

You should use ETM.

Thanks vlad, that's the impression I got. It makes sense to focus efforts on one rather than keep two very similar approaches up to date.

Hi guys I was wondering if ETM support's e-mail attachments? if so can anybody point me to the right direction? I am using version 4.0 at the moment.

Muddinu: yes, the ETM has attachment support. However, since we found that the requirements for attachments vary a lot, there is no point-and-click support. You will have to write some lines of code in your event.

The events provided with the ETM combined with the core documentation should provide a nice starting point.

Thank-you for your help I'll try it out.

Managed to make it work , Thank-you again for the help.

Awesome, good to hear!

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details