Changes:
* Fix script/about in production mode. #370 [Cheah Chu Yeow, Xavier
Noria, David Krmpotic]
* Add the gem load paths before the framework is loaded, so certain
gems like RedCloth and BlueCloth can be frozen.
* Fix discrepancies with loading rails/init.rb from gems.
* Plugins check for the gem init path (rails/init.rb) before the
standard plugin init path (init.rb) [Jacek Becela]
* Wrapped Rails.env in StringInquirer so you can do
Rails.env.development? [DHH]
* Fixed that RailsInfoController wasn't considering all requests local
in development mode (Edgard Castro) [#310 state:resolved]
Changes:
* Fix :cookie_only to correctly avoid session fixation attacks (CVE-2007-6077)
* Fix regression where the association would not construct new finder
SQL on sav e causing bogus queries for "WHERE owner_id = NULL" even
after owner was saved.
Changes:
* Correct RAILS_GEM_VERSION regexp. Use =version gem requirement instead of
~>version so you don't get surprised by a beta gem in production. This
change means upgrading to 1.2.5 will require a boot.rb upgrade.
* Move custom inflections example so available before route generation.
* Add a new rake task to aid debugging of named routes.
* use Gem.find_name instead of search when freezing gems. Prevent false
positives for other gems with rails in the name. Closes#8729 [wselman]
* Fix syntax error in dispatcher than wrecked failsafe responses.
* Add Active Resource to rails:freeze:edge and drop Action Web Service.
* Give generate scaffold a more descriptive database message. Closes#7316
* Canonicalize RAILS_ROOT by using File.expand_path on Windows, which doesn't
have to worry about symlinks, and Pathname#realpath elsewhere, which
respects symlinks in relative paths but is incompatible with Windows. #6755
[Jeremy Kemper, trevor]
Changes:
* Fix gem deprecation warnings, which also means depending on RubyGems 0.9.0+
[Chad Fowler]
* Require the dispatcher for Rails::Configuration#to_prepare. [Rick]
Rails is a full-stack framework for developing database-backed web
applications according to the Model-View-Control pattern. From the
Ajax in the view, to the request and response in the controller, to
the domain model wrapping the database, Rails gives you a pure-Ruby
development environment. To go live, all you need to add is a
database and a web server.
