Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve reimbursement emails #1139

Closed

Conversation

kennyadsl
Copy link
Member

@kennyadsl kennyadsl commented May 11, 2016

This PR adds some improvements to the reimbursement email:

  • it allows testing emails like other ones with the rails preview. To watch and work with this preview a real reimbursement (persisted in the database) is needed so it adds a reimbursement sample that is loaded with the spree_sample:load task and attached to one order previously created.
  • it adds a basic html version of the reimbursement email.

I'm open to squash commits or discuss any change or improvement.

@kennyadsl
Copy link
Member Author

What about to also adding a preference for Reimbursement Mailer class, similar to Spree::CartonMailer ?

subject = (resend ? "[#{Spree.t(:resend).upcase}] " : '')
subject += "#{store.name} #{Spree.t('reimbursement_mailer.reimbursement_email.subject')} ##{@reimbursement.order.number}"
mail(to: @reimbursement.order.email, from: from_address(store), subject: subject)
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you PR this in a separate PR that just fixes the indentation? I'm good with the change, just don't want to mix it up with some of the other stuff in this PR.

@mamhoff
Copy link
Contributor

mamhoff commented May 13, 2016

I would like this to be split up into one PR for fixing indentation, one for adding the HTML view and preview, and one for changing the Text version of the E-Mail.

@kennyadsl kennyadsl closed this May 14, 2016
@kennyadsl kennyadsl deleted the improve_reimbursement_emails branch May 14, 2016 05:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants