aboutsummaryrefslogtreecommitdiffstats
path: root/actionmailer/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* Improve docs, changelog and release notes for Action Mailer default_options=Carlos Antonio da Silva2012-07-061-2/+2
| | | | [ci skip]
* Introduce config.action_mailer.default_from=Robert Pankowecki2012-07-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Allows to easily set :from, :replay_to, etc. options in config/application.rb using simple syntax: config.action_mailer.default_options = {from:"no-replay@example.org"} This was not possible using #default method because config.action_mailer.default(from: "no-replay@example.org") is interpreated as reader method and just returns nil. It would not call ActionMailer::Base.default method. The only way of calling this method from config/application.rb was to use the direct syntax which looks ugly in my opinion: config.assets.enabled = false config.assets.version = '1.0' config.encoding = "utf-8" config.action_mailer.default_url_options= { host:"example.org", protocol:"https" } ActionMailer::Base.default(from: "no-replay@example.org")
* Updated ChangelogsBrian Cardarella2012-06-231-0/+2
|
* raise an error if no implicit mailer template could be foundDamien Mathieu2012-06-201-0/+4
|
* Sync CHANGLOG with the 3-2-stable branchRafael Mendonça França2012-06-011-0/+10
|
* Update Rails 3.2.3 release date in changelogs as March 30, 2012Michael de Silva2012-04-161-1/+1
| | | | | The release date details have been taken from http://weblog.rubyonrails.org/2012/3/30/ann-rails-3-2-3-has-been-released/
* Fix my name in the CHANGELOG to follow the conventionRafael Mendonça França2012-03-091-0/+6
| | | | Also add missing entries and use the formating convention
* fix incorrect changelog headings [ci skip].Vijay Dev2012-03-091-1/+1
| | | | Last commit message should not have said 'Rails 4' either
* changelog updates for Rails 4 [ci skip]Vijay Dev2012-03-091-1/+1
|
* Update changelogs with rails 3.0-stable branch infoPaco Guzman2012-02-251-1/+53
|
* Convert CHANGELOGs to Markdown format.Jon Leighton2011-11-041-0/+449
Reasons: * Markdown reads well as plain text, but can also be formatted. * It will make it easier for people to read on the web as Github formats the Markdown nicely. * It will encourage a level of consistency when people are writing CHANGELOG entries. The script used to perform the conversion is at https://gist.github.com/1339263