¿Reemplazar email/notification.html mediante un Plugin personalizado: consejos?

Desarrollador
1

I’ve reached a bit of an impasse and I’m looking for a spot of help.

As part of our switchover to Discourse, we want to change the design of the default email templates and obviously, as only the copy can be changed via the control panel, we figured we’d need to substitute the email templates by building a plugin that allows our email templates to persist between upgrades.

I’ve sussed out how to override the digests, thanks to this thread here:

…however, this doesn’t help when it comes to the notification.html.erb template, which seems to be impervious to ::ActionMailer::Base.prepend_view_path.

Poking into the business end of user_notifications.rb, I noticed this:

html = UserNotificationRenderer.new(Rails.configuration.paths["app/views"]).render(
          template: 'email/notification',
          format: :html,
          locals: { context_posts: context_posts,
                    reached_limit: reached_limit,
                    post: post,
                    in_reply_to_post: in_reply_to_post,
                    classes: Rtl.new(user).css_class
          }
)

I assume this is what is responsible for setting the location of the template file to be used, but see no obvious way to manipulate this without overriding the method in a plugin and admittedly, my experience with Ruby is somewhat limited, so any help you could provide would be very much appreciated.

2

I believe we have plans to make email templates more customizable in the near future, don’t we @awesomerobot?

3

Well, since yesterdaty, I’ve managed to make something happen. I don’t think it’s particularly clean, but here it is.

In my plugin.rb file:

# This attempts to override the Notification Emails by sliding in 
# our custom template directory first.
require_dependency 'user_notifications'
module ::UserNotificationsOverride
    def send_notification_email(opts)
        Rails.configuration.paths["app/views"].unshift(File.expand_path("../templates", __FILE__))
        super(opts)
    end
end

class ::UserNotifications
    prepend ::UserNotificationsOverride
end

…and then adjacent to the plugin file is a template/ directory that contains customised .erb files using the same structure as below /app/views. So my plugin now looks like:

/my-email-plugin
├── plugin.rb
└── templates
    └── email
        ├── _post.html.erb
        ├── invite.html.erb
        ├── notification.html.erb
        └── template.html.erb

What I wanted to do was shift my custom templates folder ahead of the default, in an attempt to replicate what the ::ActionMailer::Base.prepend_view_path line was doing, but without breaking anything else or by carbon-copying the entire send_notification_email method for the sake of changing one line.

If you can think of any ways to improve this, then please do share. :slight_smile:

4

¿Funcionó esto para ti y sigue funcionando?

Intenté crear un plugin usando tu código en plugin.rb y la estructura de plantillas, pero al intentar reconstruir la aplicación después de agregar el plugin en containers/app.yml, falla con el siguiente error:

LoadError: No se puede cargar el archivo – user_notifications.rb

5

He descubierto cuál era el problema. El código de plugin.rb debe colocarse dentro de after_initialize:

after_initialize do
    require_dependency 'user_notifications'
    module ::UserNotificationsOverride
        def send_notification_email(opts)
            Rails.configuration.paths["app/views"].unshift(File.expand_path("../templates", __FILE__))
            super(opts)
        end
    end

    class ::UserNotifications
        prepend ::UserNotificationsOverride
    end
end

Ahora me funciona perfectamente. ¡Gracias por compartir este método!

6

Nota, @neil acaba de fusionar esto:

¿Esta nueva característica central resuelve la necesidad subyacente que tenías para crear este plugin?

7

El contenido de las plantillas notification.html.erb y _*post.html.erb aún no es personalizable, por lo que tendremos que encontrar una forma de resolverlo en la parte 2 del trabajo de personalización de correos electrónicos.