rails 4.1.0 → 5.2.0

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.


This version of rails might be problematic. Click here for more details.

Files changed (284) hide show
  1. checksums.yaml +5 -5
  2. data/README.md +33 -19
  3. metadata +65 -310
  4. data/guides/CHANGELOG.md +0 -13
  5. data/guides/Rakefile +0 -77
  6. data/guides/assets/images/akshaysurve.jpg +0 -0
  7. data/guides/assets/images/belongs_to.png +0 -0
  8. data/guides/assets/images/book_icon.gif +0 -0
  9. data/guides/assets/images/bullet.gif +0 -0
  10. data/guides/assets/images/chapters_icon.gif +0 -0
  11. data/guides/assets/images/check_bullet.gif +0 -0
  12. data/guides/assets/images/credits_pic_blank.gif +0 -0
  13. data/guides/assets/images/csrf.png +0 -0
  14. data/guides/assets/images/edge_badge.png +0 -0
  15. data/guides/assets/images/favicon.ico +0 -0
  16. data/guides/assets/images/feature_tile.gif +0 -0
  17. data/guides/assets/images/footer_tile.gif +0 -0
  18. data/guides/assets/images/fxn.png +0 -0
  19. data/guides/assets/images/getting_started/article_with_comments.png +0 -0
  20. data/guides/assets/images/getting_started/challenge.png +0 -0
  21. data/guides/assets/images/getting_started/confirm_dialog.png +0 -0
  22. data/guides/assets/images/getting_started/forbidden_attributes_for_new_article.png +0 -0
  23. data/guides/assets/images/getting_started/form_with_errors.png +0 -0
  24. data/guides/assets/images/getting_started/index_action_with_edit_link.png +0 -0
  25. data/guides/assets/images/getting_started/new_article.png +0 -0
  26. data/guides/assets/images/getting_started/rails_welcome.png +0 -0
  27. data/guides/assets/images/getting_started/routing_error_no_controller.png +0 -0
  28. data/guides/assets/images/getting_started/routing_error_no_route_matches.png +0 -0
  29. data/guides/assets/images/getting_started/show_action_for_articles.png +0 -0
  30. data/guides/assets/images/getting_started/template_is_missing_articles_new.png +0 -0
  31. data/guides/assets/images/getting_started/unknown_action_create_for_articles.png +0 -0
  32. data/guides/assets/images/getting_started/unknown_action_new_for_articles.png +0 -0
  33. data/guides/assets/images/grey_bullet.gif +0 -0
  34. data/guides/assets/images/habtm.png +0 -0
  35. data/guides/assets/images/has_many.png +0 -0
  36. data/guides/assets/images/has_many_through.png +0 -0
  37. data/guides/assets/images/has_one.png +0 -0
  38. data/guides/assets/images/has_one_through.png +0 -0
  39. data/guides/assets/images/header_backdrop.png +0 -0
  40. data/guides/assets/images/header_tile.gif +0 -0
  41. data/guides/assets/images/i18n/demo_html_safe.png +0 -0
  42. data/guides/assets/images/i18n/demo_localized_pirate.png +0 -0
  43. data/guides/assets/images/i18n/demo_translated_en.png +0 -0
  44. data/guides/assets/images/i18n/demo_translated_pirate.png +0 -0
  45. data/guides/assets/images/i18n/demo_translation_missing.png +0 -0
  46. data/guides/assets/images/i18n/demo_untranslated.png +0 -0
  47. data/guides/assets/images/icons/README +0 -5
  48. data/guides/assets/images/icons/callouts/1.png +0 -0
  49. data/guides/assets/images/icons/callouts/10.png +0 -0
  50. data/guides/assets/images/icons/callouts/11.png +0 -0
  51. data/guides/assets/images/icons/callouts/12.png +0 -0
  52. data/guides/assets/images/icons/callouts/13.png +0 -0
  53. data/guides/assets/images/icons/callouts/14.png +0 -0
  54. data/guides/assets/images/icons/callouts/15.png +0 -0
  55. data/guides/assets/images/icons/callouts/2.png +0 -0
  56. data/guides/assets/images/icons/callouts/3.png +0 -0
  57. data/guides/assets/images/icons/callouts/4.png +0 -0
  58. data/guides/assets/images/icons/callouts/5.png +0 -0
  59. data/guides/assets/images/icons/callouts/6.png +0 -0
  60. data/guides/assets/images/icons/callouts/7.png +0 -0
  61. data/guides/assets/images/icons/callouts/8.png +0 -0
  62. data/guides/assets/images/icons/callouts/9.png +0 -0
  63. data/guides/assets/images/icons/caution.png +0 -0
  64. data/guides/assets/images/icons/example.png +0 -0
  65. data/guides/assets/images/icons/home.png +0 -0
  66. data/guides/assets/images/icons/important.png +0 -0
  67. data/guides/assets/images/icons/next.png +0 -0
  68. data/guides/assets/images/icons/note.png +0 -0
  69. data/guides/assets/images/icons/prev.png +0 -0
  70. data/guides/assets/images/icons/tip.png +0 -0
  71. data/guides/assets/images/icons/up.png +0 -0
  72. data/guides/assets/images/icons/warning.png +0 -0
  73. data/guides/assets/images/nav_arrow.gif +0 -0
  74. data/guides/assets/images/oscardelben.jpg +0 -0
  75. data/guides/assets/images/polymorphic.png +0 -0
  76. data/guides/assets/images/radar.png +0 -0
  77. data/guides/assets/images/rails4_features.png +0 -0
  78. data/guides/assets/images/rails_guides_kindle_cover.jpg +0 -0
  79. data/guides/assets/images/rails_guides_logo.gif +0 -0
  80. data/guides/assets/images/rails_logo_remix.gif +0 -0
  81. data/guides/assets/images/session_fixation.png +0 -0
  82. data/guides/assets/images/tab_grey.gif +0 -0
  83. data/guides/assets/images/tab_info.gif +0 -0
  84. data/guides/assets/images/tab_note.gif +0 -0
  85. data/guides/assets/images/tab_red.gif +0 -0
  86. data/guides/assets/images/tab_yellow.gif +0 -0
  87. data/guides/assets/images/tab_yellow.png +0 -0
  88. data/guides/assets/images/vijaydev.jpg +0 -0
  89. data/guides/assets/javascripts/guides.js +0 -53
  90. data/guides/assets/javascripts/jquery.min.js +0 -4
  91. data/guides/assets/javascripts/responsive-tables.js +0 -43
  92. data/guides/assets/javascripts/syntaxhighlighter/shBrushAS3.js +0 -59
  93. data/guides/assets/javascripts/syntaxhighlighter/shBrushAppleScript.js +0 -75
  94. data/guides/assets/javascripts/syntaxhighlighter/shBrushBash.js +0 -59
  95. data/guides/assets/javascripts/syntaxhighlighter/shBrushCSharp.js +0 -65
  96. data/guides/assets/javascripts/syntaxhighlighter/shBrushColdFusion.js +0 -100
  97. data/guides/assets/javascripts/syntaxhighlighter/shBrushCpp.js +0 -97
  98. data/guides/assets/javascripts/syntaxhighlighter/shBrushCss.js +0 -91
  99. data/guides/assets/javascripts/syntaxhighlighter/shBrushDelphi.js +0 -55
  100. data/guides/assets/javascripts/syntaxhighlighter/shBrushDiff.js +0 -41
  101. data/guides/assets/javascripts/syntaxhighlighter/shBrushErlang.js +0 -52
  102. data/guides/assets/javascripts/syntaxhighlighter/shBrushGroovy.js +0 -67
  103. data/guides/assets/javascripts/syntaxhighlighter/shBrushJScript.js +0 -52
  104. data/guides/assets/javascripts/syntaxhighlighter/shBrushJava.js +0 -57
  105. data/guides/assets/javascripts/syntaxhighlighter/shBrushJavaFX.js +0 -58
  106. data/guides/assets/javascripts/syntaxhighlighter/shBrushPerl.js +0 -72
  107. data/guides/assets/javascripts/syntaxhighlighter/shBrushPhp.js +0 -88
  108. data/guides/assets/javascripts/syntaxhighlighter/shBrushPlain.js +0 -33
  109. data/guides/assets/javascripts/syntaxhighlighter/shBrushPowerShell.js +0 -74
  110. data/guides/assets/javascripts/syntaxhighlighter/shBrushPython.js +0 -64
  111. data/guides/assets/javascripts/syntaxhighlighter/shBrushRuby.js +0 -55
  112. data/guides/assets/javascripts/syntaxhighlighter/shBrushSass.js +0 -94
  113. data/guides/assets/javascripts/syntaxhighlighter/shBrushScala.js +0 -51
  114. data/guides/assets/javascripts/syntaxhighlighter/shBrushSql.js +0 -66
  115. data/guides/assets/javascripts/syntaxhighlighter/shBrushVb.js +0 -56
  116. data/guides/assets/javascripts/syntaxhighlighter/shBrushXml.js +0 -69
  117. data/guides/assets/javascripts/syntaxhighlighter/shCore.js +0 -17
  118. data/guides/assets/stylesheets/fixes.css +0 -16
  119. data/guides/assets/stylesheets/kindle.css +0 -11
  120. data/guides/assets/stylesheets/main.css +0 -710
  121. data/guides/assets/stylesheets/print.css +0 -52
  122. data/guides/assets/stylesheets/reset.css +0 -43
  123. data/guides/assets/stylesheets/responsive-tables.css +0 -50
  124. data/guides/assets/stylesheets/style.css +0 -13
  125. data/guides/assets/stylesheets/syntaxhighlighter/shCore.css +0 -226
  126. data/guides/assets/stylesheets/syntaxhighlighter/shCoreDefault.css +0 -328
  127. data/guides/assets/stylesheets/syntaxhighlighter/shCoreDjango.css +0 -331
  128. data/guides/assets/stylesheets/syntaxhighlighter/shCoreEclipse.css +0 -339
  129. data/guides/assets/stylesheets/syntaxhighlighter/shCoreEmacs.css +0 -324
  130. data/guides/assets/stylesheets/syntaxhighlighter/shCoreFadeToGrey.css +0 -328
  131. data/guides/assets/stylesheets/syntaxhighlighter/shCoreMDUltra.css +0 -324
  132. data/guides/assets/stylesheets/syntaxhighlighter/shCoreMidnight.css +0 -324
  133. data/guides/assets/stylesheets/syntaxhighlighter/shCoreRDark.css +0 -324
  134. data/guides/assets/stylesheets/syntaxhighlighter/shThemeDefault.css +0 -117
  135. data/guides/assets/stylesheets/syntaxhighlighter/shThemeDjango.css +0 -120
  136. data/guides/assets/stylesheets/syntaxhighlighter/shThemeEclipse.css +0 -128
  137. data/guides/assets/stylesheets/syntaxhighlighter/shThemeEmacs.css +0 -113
  138. data/guides/assets/stylesheets/syntaxhighlighter/shThemeFadeToGrey.css +0 -117
  139. data/guides/assets/stylesheets/syntaxhighlighter/shThemeMDUltra.css +0 -113
  140. data/guides/assets/stylesheets/syntaxhighlighter/shThemeMidnight.css +0 -113
  141. data/guides/assets/stylesheets/syntaxhighlighter/shThemeRDark.css +0 -113
  142. data/guides/assets/stylesheets/syntaxhighlighter/shThemeRailsGuides.css +0 -116
  143. data/guides/bug_report_templates/action_controller_gem.rb +0 -47
  144. data/guides/bug_report_templates/action_controller_master.rb +0 -53
  145. data/guides/bug_report_templates/active_record_gem.rb +0 -40
  146. data/guides/bug_report_templates/active_record_master.rb +0 -49
  147. data/guides/code/getting_started/Gemfile +0 -40
  148. data/guides/code/getting_started/Gemfile.lock +0 -126
  149. data/guides/code/getting_started/README.rdoc +0 -28
  150. data/guides/code/getting_started/Rakefile +0 -6
  151. data/guides/code/getting_started/app/assets/javascripts/application.js +0 -15
  152. data/guides/code/getting_started/app/assets/javascripts/comments.js.coffee +0 -3
  153. data/guides/code/getting_started/app/assets/javascripts/posts.js.coffee +0 -3
  154. data/guides/code/getting_started/app/assets/javascripts/welcome.js.coffee +0 -3
  155. data/guides/code/getting_started/app/assets/stylesheets/application.css +0 -13
  156. data/guides/code/getting_started/app/assets/stylesheets/comments.css.scss +0 -3
  157. data/guides/code/getting_started/app/assets/stylesheets/posts.css.scss +0 -3
  158. data/guides/code/getting_started/app/assets/stylesheets/welcome.css.scss +0 -3
  159. data/guides/code/getting_started/app/controllers/application_controller.rb +0 -5
  160. data/guides/code/getting_started/app/controllers/comments_controller.rb +0 -23
  161. data/guides/code/getting_started/app/controllers/posts_controller.rb +0 -53
  162. data/guides/code/getting_started/app/controllers/welcome_controller.rb +0 -4
  163. data/guides/code/getting_started/app/helpers/application_helper.rb +0 -2
  164. data/guides/code/getting_started/app/helpers/comments_helper.rb +0 -2
  165. data/guides/code/getting_started/app/helpers/posts_helper.rb +0 -2
  166. data/guides/code/getting_started/app/helpers/welcome_helper.rb +0 -2
  167. data/guides/code/getting_started/app/models/comment.rb +0 -3
  168. data/guides/code/getting_started/app/models/post.rb +0 -7
  169. data/guides/code/getting_started/app/views/comments/_comment.html.erb +0 -15
  170. data/guides/code/getting_started/app/views/comments/_form.html.erb +0 -13
  171. data/guides/code/getting_started/app/views/layouts/application.html.erb +0 -14
  172. data/guides/code/getting_started/app/views/posts/_form.html.erb +0 -27
  173. data/guides/code/getting_started/app/views/posts/edit.html.erb +0 -5
  174. data/guides/code/getting_started/app/views/posts/index.html.erb +0 -21
  175. data/guides/code/getting_started/app/views/posts/new.html.erb +0 -5
  176. data/guides/code/getting_started/app/views/posts/show.html.erb +0 -18
  177. data/guides/code/getting_started/app/views/welcome/index.html.erb +0 -4
  178. data/guides/code/getting_started/bin/bundle +0 -4
  179. data/guides/code/getting_started/bin/rails +0 -4
  180. data/guides/code/getting_started/bin/rake +0 -4
  181. data/guides/code/getting_started/config.ru +0 -4
  182. data/guides/code/getting_started/config/application.rb +0 -18
  183. data/guides/code/getting_started/config/boot.rb +0 -4
  184. data/guides/code/getting_started/config/database.yml +0 -25
  185. data/guides/code/getting_started/config/environment.rb +0 -5
  186. data/guides/code/getting_started/config/environments/development.rb +0 -30
  187. data/guides/code/getting_started/config/environments/production.rb +0 -80
  188. data/guides/code/getting_started/config/environments/test.rb +0 -36
  189. data/guides/code/getting_started/config/initializers/backtrace_silencers.rb +0 -7
  190. data/guides/code/getting_started/config/initializers/filter_parameter_logging.rb +0 -4
  191. data/guides/code/getting_started/config/initializers/inflections.rb +0 -16
  192. data/guides/code/getting_started/config/initializers/locale.rb +0 -9
  193. data/guides/code/getting_started/config/initializers/mime_types.rb +0 -5
  194. data/guides/code/getting_started/config/initializers/secret_token.rb +0 -12
  195. data/guides/code/getting_started/config/initializers/session_store.rb +0 -3
  196. data/guides/code/getting_started/config/initializers/wrap_parameters.rb +0 -14
  197. data/guides/code/getting_started/config/locales/en.yml +0 -23
  198. data/guides/code/getting_started/config/routes.rb +0 -7
  199. data/guides/code/getting_started/db/migrate/20130122042648_create_posts.rb +0 -10
  200. data/guides/code/getting_started/db/migrate/20130122045842_create_comments.rb +0 -11
  201. data/guides/code/getting_started/db/schema.rb +0 -33
  202. data/guides/code/getting_started/db/seeds.rb +0 -7
  203. data/guides/code/getting_started/public/404.html +0 -60
  204. data/guides/code/getting_started/public/422.html +0 -60
  205. data/guides/code/getting_started/public/500.html +0 -59
  206. data/guides/code/getting_started/public/favicon.ico +0 -0
  207. data/guides/code/getting_started/public/robots.txt +0 -5
  208. data/guides/code/getting_started/test/controllers/comments_controller_test.rb +0 -7
  209. data/guides/code/getting_started/test/controllers/posts_controller_test.rb +0 -7
  210. data/guides/code/getting_started/test/controllers/welcome_controller_test.rb +0 -9
  211. data/guides/code/getting_started/test/fixtures/comments.yml +0 -11
  212. data/guides/code/getting_started/test/fixtures/posts.yml +0 -9
  213. data/guides/code/getting_started/test/helpers/comments_helper_test.rb +0 -4
  214. data/guides/code/getting_started/test/helpers/posts_helper_test.rb +0 -4
  215. data/guides/code/getting_started/test/helpers/welcome_helper_test.rb +0 -4
  216. data/guides/code/getting_started/test/models/comment_test.rb +0 -7
  217. data/guides/code/getting_started/test/models/post_test.rb +0 -7
  218. data/guides/code/getting_started/test/test_helper.rb +0 -15
  219. data/guides/rails_guides.rb +0 -63
  220. data/guides/rails_guides/generator.rb +0 -248
  221. data/guides/rails_guides/helpers.rb +0 -53
  222. data/guides/rails_guides/indexer.rb +0 -68
  223. data/guides/rails_guides/kindle.rb +0 -119
  224. data/guides/rails_guides/levenshtein.rb +0 -31
  225. data/guides/rails_guides/markdown.rb +0 -163
  226. data/guides/rails_guides/markdown/renderer.rb +0 -82
  227. data/guides/source/2_2_release_notes.md +0 -435
  228. data/guides/source/2_3_release_notes.md +0 -621
  229. data/guides/source/3_0_release_notes.md +0 -611
  230. data/guides/source/3_1_release_notes.md +0 -556
  231. data/guides/source/3_2_release_notes.md +0 -565
  232. data/guides/source/4_0_release_notes.md +0 -276
  233. data/guides/source/4_1_release_notes.md +0 -731
  234. data/guides/source/_license.html.erb +0 -2
  235. data/guides/source/_welcome.html.erb +0 -22
  236. data/guides/source/action_controller_overview.md +0 -1175
  237. data/guides/source/action_mailer_basics.md +0 -689
  238. data/guides/source/action_view_overview.md +0 -1610
  239. data/guides/source/active_model_basics.md +0 -200
  240. data/guides/source/active_record_basics.md +0 -373
  241. data/guides/source/active_record_callbacks.md +0 -410
  242. data/guides/source/active_record_querying.md +0 -1771
  243. data/guides/source/active_record_validations.md +0 -1169
  244. data/guides/source/active_support_core_extensions.md +0 -3864
  245. data/guides/source/active_support_instrumentation.md +0 -496
  246. data/guides/source/api_documentation_guidelines.md +0 -281
  247. data/guides/source/asset_pipeline.md +0 -1163
  248. data/guides/source/association_basics.md +0 -2229
  249. data/guides/source/caching_with_rails.md +0 -354
  250. data/guides/source/command_line.md +0 -603
  251. data/guides/source/configuring.md +0 -942
  252. data/guides/source/contributing_to_ruby_on_rails.md +0 -544
  253. data/guides/source/credits.html.erb +0 -80
  254. data/guides/source/debugging_rails_applications.md +0 -707
  255. data/guides/source/development_dependencies_install.md +0 -278
  256. data/guides/source/documents.yaml +0 -194
  257. data/guides/source/engines.md +0 -1391
  258. data/guides/source/form_helpers.md +0 -1001
  259. data/guides/source/generators.md +0 -663
  260. data/guides/source/getting_started.md +0 -1947
  261. data/guides/source/i18n.md +0 -1043
  262. data/guides/source/index.html.erb +0 -27
  263. data/guides/source/initialization.md +0 -657
  264. data/guides/source/kindle/copyright.html.erb +0 -1
  265. data/guides/source/kindle/layout.html.erb +0 -27
  266. data/guides/source/kindle/rails_guides.opf.erb +0 -52
  267. data/guides/source/kindle/toc.html.erb +0 -24
  268. data/guides/source/kindle/toc.ncx.erb +0 -64
  269. data/guides/source/kindle/welcome.html.erb +0 -5
  270. data/guides/source/layout.html.erb +0 -146
  271. data/guides/source/layouts_and_rendering.md +0 -1226
  272. data/guides/source/maintenance_policy.md +0 -56
  273. data/guides/source/migrations.md +0 -1108
  274. data/guides/source/nested_model_forms.md +0 -225
  275. data/guides/source/plugins.md +0 -444
  276. data/guides/source/rails_application_templates.md +0 -248
  277. data/guides/source/rails_on_rack.md +0 -333
  278. data/guides/source/routing.md +0 -1115
  279. data/guides/source/ruby_on_rails_guides_guidelines.md +0 -128
  280. data/guides/source/security.md +0 -1018
  281. data/guides/source/testing.md +0 -1057
  282. data/guides/source/upgrading_ruby_on_rails.md +0 -890
  283. data/guides/source/working_with_javascript_in_rails.md +0 -405
  284. data/guides/w3c_validator.rb +0 -95
@@ -1,890 +0,0 @@
1
- A Guide for Upgrading Ruby on Rails
2
- ===================================
3
-
4
- This guide provides steps to be followed when you upgrade your applications to a newer version of Ruby on Rails. These steps are also available in individual release guides.
5
-
6
- General Advice
7
- --------------
8
-
9
- Before attempting to upgrade an existing application, you should be sure you have a good reason to upgrade. You need to balance out several factors: the need for new features, the increasing difficulty of finding support for old code, and your available time and skills, to name a few.
10
-
11
- ### Test Coverage
12
-
13
- The best way to be sure that your application still works after upgrading is to have good test coverage before you start the process. If you don't have automated tests that exercise the bulk of your application, you'll need to spend time manually exercising all the parts that have changed. In the case of a Rails upgrade, that will mean every single piece of functionality in the application. Do yourself a favor and make sure your test coverage is good _before_ you start an upgrade.
14
-
15
- ### Ruby Versions
16
-
17
- Rails generally stays close to the latest released Ruby version when it's released:
18
-
19
- * Rails 3 and above require Ruby 1.8.7 or higher. Support for all of the previous Ruby versions has been dropped officially. You should upgrade as early as possible.
20
- * Rails 3.2.x is the last branch to support Ruby 1.8.7.
21
- * Rails 4 prefers Ruby 2.0 and requires 1.9.3 or newer.
22
-
23
- TIP: Ruby 1.8.7 p248 and p249 have marshaling bugs that crash Rails. Ruby Enterprise Edition has these fixed since the release of 1.8.7-2010.02. On the 1.9 front, Ruby 1.9.1 is not usable because it outright segfaults, so if you want to use 1.9.x, jump straight to 1.9.3 for smooth sailing.
24
-
25
- Upgrading from Rails 4.0 to Rails 4.1
26
- -------------------------------------
27
-
28
- NOTE: This section is a work in progress.
29
-
30
- ### CSRF protection from remote `<script>` tags
31
-
32
- Or, "whaaat my tests are failing!!!?"
33
-
34
- Cross-site request forgery (CSRF) protection now covers GET requests with
35
- JavaScript responses, too. That prevents a third-party site from referencing
36
- your JavaScript URL and attempting to run it to extract sensitive data.
37
-
38
- This means that your functional and integration tests that use
39
-
40
- ```ruby
41
- get :index, format: :js
42
- ```
43
-
44
- will now trigger CSRF protection. Switch to
45
-
46
- ```ruby
47
- xhr :get, :index, format: :js
48
- ```
49
-
50
- to explicitly test an XmlHttpRequest.
51
-
52
- If you really mean to load JavaScript from remote `<script>` tags, skip CSRF
53
- protection on that action.
54
-
55
- ### Spring
56
-
57
- If you want to use Spring as your application preloader you need to:
58
-
59
- 1. Add `gem 'spring', group: :development` to your `Gemfile`.
60
- 2. Install spring using `bundle install`.
61
- 3. Springify your binstubs with `bundle exec spring binstub --all`.
62
-
63
- NOTE: User defined rake tasks will run in the `development` environment by
64
- default. If you want them to run in other environments consult the
65
- [Spring README](https://github.com/rails/spring#rake).
66
-
67
- ### `config/secrets.yml`
68
-
69
- If you want to use the new `secrets.yml` convention to store your application's
70
- secrets, you need to:
71
-
72
- 1. Create a `secrets.yml` file in your `config` folder with the following content:
73
-
74
- ```yaml
75
- development:
76
- secret_key_base:
77
-
78
- test:
79
- secret_key_base:
80
-
81
- production:
82
- secret_key_base:
83
- ```
84
-
85
- 2. Copy the existing `secret_key_base` from the `secret_token.rb` initializer to
86
- `secrets.yml` under the `production` section.
87
-
88
- 3. Remove the `secret_token.rb` initializer.
89
-
90
- 4. Use `rake secret` to generate new keys for the `development` and `test` sections.
91
-
92
- 5. Restart your server.
93
-
94
- ### Changes to test helper
95
-
96
- If your test helper contains a call to
97
- `ActiveRecord::Migration.check_pending!` this can be removed. The check
98
- is now done automatically when you `require 'test_help'`, although
99
- leaving this line in your helper is not harmful in any way.
100
-
101
- ### Cookies serializer
102
-
103
- Applications created before Rails 4.1 uses `Marshal` to serialize cookie values into
104
- the signed and encrypted cookie jars. If you want to use the new `JSON`-based format
105
- in your application, you can add an initializer file with the following content:
106
-
107
- ```ruby
108
- Rails.application.config.action_dispatch.cookies_serializer = :hybrid
109
- ```
110
-
111
- This would transparently migrate your existing `Marshal`-serialized cookies into the
112
- new `JSON`-based format.
113
-
114
- When using the `:json` or `:hybrid` serializer, you should beware that not all
115
- Ruby objects can be serialized as JSON. For example, `Date` and `Time` objects
116
- will be serialized as strings, and `Hash`es will have their keys stringified.
117
-
118
- ```ruby
119
- class CookiesController < ApplicationController
120
- def set_cookie
121
- cookies.encrypted[:expiration_date] = Date.tomorrow # => Thu, 20 Mar 2014
122
- redirect_to action: 'read_cookie'
123
- end
124
-
125
- def read_cookie
126
- cookies.encrypted[:expiration_date] # => "2014-03-20"
127
- end
128
- end
129
- ```
130
-
131
- It's advisable that you only store simple data (strings and numbers) in cookies.
132
- If you have to store complex objects, you would need to handle the conversion
133
- manually when reading the values on subsequent requests.
134
-
135
- If you use the cookie session store, this would apply to the `session` and
136
- `flash` hash as well.
137
-
138
- ### Flash structure changes
139
-
140
- Flash message keys are
141
- [normalized to strings](https://github.com/rails/rails/commit/a668beffd64106a1e1fedb71cc25eaaa11baf0c1). They
142
- can still be accessed using either symbols or strings. Lopping through the flash
143
- will always yield string keys:
144
-
145
- ```ruby
146
- flash["string"] = "a string"
147
- flash[:symbol] = "a symbol"
148
-
149
- # Rails < 4.1
150
- flash.keys # => ["string", :symbol]
151
-
152
- # Rails >= 4.1
153
- flash.keys # => ["string", "symbol"]
154
- ```
155
-
156
- Make sure you are comparing Flash message keys against strings.
157
-
158
- ### Changes in JSON handling
159
-
160
- There are a few major changes related to JSON handling in Rails 4.1.
161
-
162
- #### MultiJSON removal
163
-
164
- MultiJSON has reached its [end-of-life](https://github.com/rails/rails/pull/10576)
165
- and has been removed from Rails.
166
-
167
- If your application currently depend on MultiJSON directly, you have a few options:
168
-
169
- 1. Add 'multi_json' to your Gemfile. Note that this might cease to work in the future
170
-
171
- 2. Migrate away from MultiJSON by using `obj.to_json`, and `JSON.parse(str)` instead.
172
-
173
- WARNING: Do not simply replace `MultiJson.dump` and `MultiJson.load` with
174
- `JSON.dump` and `JSON.load`. These JSON gem APIs are meant for serializing and
175
- deserializing arbitrary Ruby objects and are generally [unsafe](http://www.ruby-doc.org/stdlib-2.0.0/libdoc/json/rdoc/JSON.html#method-i-load).
176
-
177
- #### JSON gem compatibility
178
-
179
- Historically, Rails had some compatibility issues with the JSON gem. Using
180
- `JSON.generate` and `JSON.dump` inside a Rails application could produce
181
- unexpected errors.
182
-
183
- Rails 4.1 fixed these issues by isolating its own encoder from the JSON gem. The
184
- JSON gem APIs will function as normal, but they will not have access to any
185
- Rails-specific features. For example:
186
-
187
- ```ruby
188
- class FooBar
189
- def as_json(options = nil)
190
- { foo: 'bar' }
191
- end
192
- end
193
-
194
- >> FooBar.new.to_json # => "{\"foo\":\"bar\"}"
195
- >> JSON.generate(FooBar.new, quirks_mode: true) # => "\"#<FooBar:0x007fa80a481610>\""
196
- ```
197
-
198
- #### New JSON encoder
199
-
200
- The JSON encoder in Rails 4.1 has been rewritten to take advantage of the JSON
201
- gem. For most applications, this should be a transparent change. However, as
202
- part of the rewrite, the following features have been removed from the encoder:
203
-
204
- 1. Circular data structure detection
205
- 2. Support for the `encode_json` hook
206
- 3. Option to encode `BigDecimal` objects as numbers instead of strings
207
-
208
- If your application depends on one of these features, you can get them back by
209
- adding the [`activesupport-json_encoder`](https://github.com/rails/activesupport-json_encoder)
210
- gem to your Gemfile.
211
-
212
- ### Usage of `return` within inline callback blocks
213
-
214
- Previously, Rails allowed inline callback blocks to use `return` this way:
215
-
216
- ```ruby
217
- class ReadOnlyModel < ActiveRecord::Base
218
- before_save { return false } # BAD
219
- end
220
- ```
221
-
222
- This behaviour was never intentionally supported. Due to a change in the internals
223
- of `ActiveSupport::Callbacks`, this is no longer allowed in Rails 4.1. Using a
224
- `return` statement in an inline callback block causes a `LocalJumpError` to
225
- be raised when the callback is executed.
226
-
227
- Inline callback blocks using `return` can be refactored to evaluate to the
228
- returned value:
229
-
230
- ```ruby
231
- class ReadOnlyModel < ActiveRecord::Base
232
- before_save { false } # GOOD
233
- end
234
- ```
235
-
236
- Alternatively, if `return` is preferred it is recommended to explicitly define
237
- a method:
238
-
239
- ```ruby
240
- class ReadOnlyModel < ActiveRecord::Base
241
- before_save :before_save_callback # GOOD
242
-
243
- private
244
- def before_save_callback
245
- return false
246
- end
247
- end
248
- ```
249
-
250
- This change applies to most places in Rails where callbacks are used, including
251
- Active Record and Active Model callbacks, as well as filters in Action
252
- Controller (e.g. `before_action`).
253
-
254
- See [this pull request](https://github.com/rails/rails/pull/13271) for more
255
- details.
256
-
257
- ### Methods defined in Active Record fixtures
258
-
259
- Rails 4.1 evaluates each fixture's ERB in a separate context, so helper methods
260
- defined in a fixture will not be available in other fixtures.
261
-
262
- Helper methods that are used in multiple fixtures should be defined on modules
263
- included in the newly introduced `ActiveRecord::FixtureSet.context_class`, in
264
- `test_helper.rb`.
265
-
266
- ```ruby
267
- class FixtureFileHelpers
268
- def file_sha(path)
269
- Digest::SHA2.hexdigest(File.read(Rails.root.join('test/fixtures', path)))
270
- end
271
- end
272
- ActiveRecord::FixtureSet.context_class.send :include, FixtureFileHelpers
273
- ```
274
-
275
- ### I18n enforcing available locales
276
-
277
- Rails 4.1 now defaults the I18n option `enforce_available_locales` to `true`,
278
- meaning that it will make sure that all locales passed to it must be declared in
279
- the `available_locales` list.
280
-
281
- To disable it (and allow I18n to accept *any* locale option) add the following
282
- configuration to your application:
283
-
284
- ```ruby
285
- config.i18n.enforce_available_locales = false
286
- ```
287
-
288
- Note that this option was added as a security measure, to ensure user input could
289
- not be used as locale information unless previously known, so it's recommended not
290
- to disable this option unless you have a strong reason for doing so.
291
-
292
- ### Mutator methods called on Relation
293
-
294
- `Relation` no longer has mutator methods like `#map!` and `#delete_if`. Convert
295
- to an `Array` by calling `#to_a` before using these methods.
296
-
297
- It intends to prevent odd bugs and confusion in code that call mutator
298
- methods directly on the `Relation`.
299
-
300
- ```ruby
301
- # Instead of this
302
- Author.where(name: 'Hank Moody').compact!
303
-
304
- # Now you have to do this
305
- authors = Author.where(name: 'Hank Moody').to_a
306
- authors.compact!
307
- ```
308
-
309
- ### Changes on Default Scopes
310
-
311
- Default scopes are no longer overriden by chained conditions.
312
-
313
- In previous versions when you defined a `default_scope` in a model
314
- it was overriden by chained conditions in the same field. Now it
315
- is merged like any other scope.
316
-
317
- Before:
318
-
319
- ```ruby
320
- class User < ActiveRecord::Base
321
- default_scope { where state: 'pending' }
322
- scope :active, -> { where state: 'active' }
323
- scope :inactive, -> { where state: 'inactive' }
324
- end
325
-
326
- User.all
327
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'pending'
328
-
329
- User.active
330
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'active'
331
-
332
- User.where(state: 'inactive')
333
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'inactive'
334
- ```
335
-
336
- After:
337
-
338
- ```ruby
339
- class User < ActiveRecord::Base
340
- default_scope { where state: 'pending' }
341
- scope :active, -> { where state: 'active' }
342
- scope :inactive, -> { where state: 'inactive' }
343
- end
344
-
345
- User.all
346
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'pending'
347
-
348
- User.active
349
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'pending' AND "users"."state" = 'active'
350
-
351
- User.where(state: 'inactive')
352
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'pending' AND "users"."state" = 'inactive'
353
- ```
354
-
355
- To get the previous behavior it is needed to explicitly remove the
356
- `default_scope` condition using `unscoped`, `unscope`, `rewhere` or
357
- `except`.
358
-
359
- ```ruby
360
- class User < ActiveRecord::Base
361
- default_scope { where state: 'pending' }
362
- scope :active, -> { unscope(where: :state).where(state: 'active') }
363
- scope :inactive, -> { rewhere state: 'inactive' }
364
- end
365
-
366
- User.all
367
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'pending'
368
-
369
- User.active
370
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'active'
371
-
372
- User.inactive
373
- # SELECT "users".* FROM "users" WHERE "users"."state" = 'inactive'
374
- ```
375
-
376
- ### Rendering content from string
377
-
378
- Rails 4.1 introduces `:plain`, `:html`, and `:body` options to `render`. Those
379
- options are now the preferred way to render string-based content, as it allows
380
- you to specify which content type you want the response sent as.
381
-
382
- * `render :plain` will set the content type to `text/plain`
383
- * `render :html` will set the content type to `text/html`
384
- * `render :body` will *not* set the content type header.
385
-
386
- From the security standpoint, if you don't expect to have any markup in your
387
- response body, you should be using `render :plain` as most browsers will escape
388
- unsafe content in the response for you.
389
-
390
- We will be deprecating the use of `render :text` in a future version. So please
391
- start using the more precise `:plain:`, `:html`, and `:body` options instead.
392
- Using `render :text` may pose a security risk, as the content is sent as
393
- `text/html`.
394
-
395
- Upgrading from Rails 3.2 to Rails 4.0
396
- -------------------------------------
397
-
398
- If your application is currently on any version of Rails older than 3.2.x, you should upgrade to Rails 3.2 before attempting one to Rails 4.0.
399
-
400
- The following changes are meant for upgrading your application to Rails 4.0.
401
-
402
- ### HTTP PATCH
403
-
404
- Rails 4 now uses `PATCH` as the primary HTTP verb for updates when a RESTful
405
- resource is declared in `config/routes.rb`. The `update` action is still used,
406
- and `PUT` requests will continue to be routed to the `update` action as well.
407
- So, if you're using only the standard RESTful routes, no changes need to be made:
408
-
409
- ```ruby
410
- resources :users
411
- ```
412
-
413
- ```erb
414
- <%= form_for @user do |f| %>
415
- ```
416
-
417
- ```ruby
418
- class UsersController < ApplicationController
419
- def update
420
- # No change needed; PATCH will be preferred, and PUT will still work.
421
- end
422
- end
423
- ```
424
-
425
- However, you will need to make a change if you are using `form_for` to update
426
- a resource in conjunction with a custom route using the `PUT` HTTP method:
427
-
428
- ```ruby
429
- resources :users, do
430
- put :update_name, on: :member
431
- end
432
- ```
433
-
434
- ```erb
435
- <%= form_for [ :update_name, @user ] do |f| %>
436
- ```
437
-
438
- ```ruby
439
- class UsersController < ApplicationController
440
- def update_name
441
- # Change needed; form_for will try to use a non-existent PATCH route.
442
- end
443
- end
444
- ```
445
-
446
- If the action is not being used in a public API and you are free to change the
447
- HTTP method, you can update your route to use `patch` instead of `put`:
448
-
449
- `PUT` requests to `/users/:id` in Rails 4 get routed to `update` as they are
450
- today. So, if you have an API that gets real PUT requests it is going to work.
451
- The router also routes `PATCH` requests to `/users/:id` to the `update` action.
452
-
453
- ```ruby
454
- resources :users do
455
- patch :update_name, on: :member
456
- end
457
- ```
458
-
459
- If the action is being used in a public API and you can't change to HTTP method
460
- being used, you can update your form to use the `PUT` method instead:
461
-
462
- ```erb
463
- <%= form_for [ :update_name, @user ], method: :put do |f| %>
464
- ```
465
-
466
- For more on PATCH and why this change was made, see [this post](http://weblog.rubyonrails.org/2012/2/26/edge-rails-patch-is-the-new-primary-http-method-for-updates/)
467
- on the Rails blog.
468
-
469
- #### A note about media types
470
-
471
- The errata for the `PATCH` verb [specifies that a 'diff' media type should be
472
- used with `PATCH`](http://www.rfc-editor.org/errata_search.php?rfc=5789). One
473
- such format is [JSON Patch](http://tools.ietf.org/html/rfc6902). While Rails
474
- does not support JSON Patch natively, it's easy enough to add support:
475
-
476
- ```
477
- # in your controller
478
- def update
479
- respond_to do |format|
480
- format.json do
481
- # perform a partial update
482
- @post.update params[:post]
483
- end
484
-
485
- format.json_patch do
486
- # perform sophisticated change
487
- end
488
- end
489
- end
490
-
491
- # In config/initializers/json_patch.rb:
492
- Mime::Type.register 'application/json-patch+json', :json_patch
493
- ```
494
-
495
- As JSON Patch was only recently made into an RFC, there aren't a lot of great
496
- Ruby libraries yet. Aaron Patterson's
497
- [hana](https://github.com/tenderlove/hana) is one such gem, but doesn't have
498
- full support for the last few changes in the specification.
499
-
500
- ### Gemfile
501
-
502
- Rails 4.0 removed the `assets` group from Gemfile. You'd need to remove that
503
- line from your Gemfile when upgrading. You should also update your application
504
- file (in `config/application.rb`):
505
-
506
- ```ruby
507
- # Require the gems listed in Gemfile, including any gems
508
- # you've limited to :test, :development, or :production.
509
- Bundler.require(:default, Rails.env)
510
- ```
511
-
512
- ### vendor/plugins
513
-
514
- Rails 4.0 no longer supports loading plugins from `vendor/plugins`. You must replace any plugins by extracting them to gems and adding them to your Gemfile. If you choose not to make them gems, you can move them into, say, `lib/my_plugin/*` and add an appropriate initializer in `config/initializers/my_plugin.rb`.
515
-
516
- ### Active Record
517
-
518
- * Rails 4.0 has removed the identity map from Active Record, due to [some inconsistencies with associations](https://github.com/rails/rails/commit/302c912bf6bcd0fa200d964ec2dc4a44abe328a6). If you have manually enabled it in your application, you will have to remove the following config that has no effect anymore: `config.active_record.identity_map`.
519
-
520
- * The `delete` method in collection associations can now receive `Fixnum` or `String` arguments as record ids, besides records, pretty much like the `destroy` method does. Previously it raised `ActiveRecord::AssociationTypeMismatch` for such arguments. From Rails 4.0 on `delete` automatically tries to find the records matching the given ids before deleting them.
521
-
522
- * In Rails 4.0 when a column or a table is renamed the related indexes are also renamed. If you have migrations which rename the indexes, they are no longer needed.
523
-
524
- * Rails 4.0 has changed `serialized_attributes` and `attr_readonly` to class methods only. You shouldn't use instance methods since it's now deprecated. You should change them to use class methods, e.g. `self.serialized_attributes` to `self.class.serialized_attributes`.
525
-
526
- * Rails 4.0 has removed `attr_accessible` and `attr_protected` feature in favor of Strong Parameters. You can use the [Protected Attributes gem](https://github.com/rails/protected_attributes) for a smooth upgrade path.
527
-
528
- * If you are not using Protected Attributes, you can remove any options related to
529
- this gem such as `whitelist_attributes` or `mass_assignment_sanitizer` options.
530
-
531
- * Rails 4.0 requires that scopes use a callable object such as a Proc or lambda:
532
-
533
- ```ruby
534
- scope :active, where(active: true)
535
-
536
- # becomes
537
- scope :active, -> { where active: true }
538
- ```
539
-
540
- * Rails 4.0 has deprecated `ActiveRecord::Fixtures` in favor of `ActiveRecord::FixtureSet`.
541
-
542
- * Rails 4.0 has deprecated `ActiveRecord::TestCase` in favor of `ActiveSupport::TestCase`.
543
-
544
- * Rails 4.0 has deprecated the old-style hash based finder API. This means that
545
- methods which previously accepted "finder options" no longer do.
546
-
547
- * All dynamic methods except for `find_by_...` and `find_by_...!` are deprecated.
548
- Here's how you can handle the changes:
549
-
550
- * `find_all_by_...` becomes `where(...)`.
551
- * `find_last_by_...` becomes `where(...).last`.
552
- * `scoped_by_...` becomes `where(...)`.
553
- * `find_or_initialize_by_...` becomes `find_or_initialize_by(...)`.
554
- * `find_or_create_by_...` becomes `find_or_create_by(...)`.
555
-
556
- * Note that `where(...)` returns a relation, not an array like the old finders. If you require an `Array`, use `where(...).to_a`.
557
-
558
- * These equivalent methods may not execute the same SQL as the previous implementation.
559
-
560
- * To re-enable the old finders, you can use the [activerecord-deprecated_finders gem](https://github.com/rails/activerecord-deprecated_finders).
561
-
562
- ### Active Resource
563
-
564
- Rails 4.0 extracted Active Resource to its own gem. If you still need the feature you can add the [Active Resource gem](https://github.com/rails/activeresource) in your Gemfile.
565
-
566
- ### Active Model
567
-
568
- * Rails 4.0 has changed how errors attach with the `ActiveModel::Validations::ConfirmationValidator`. Now when confirmation validations fail, the error will be attached to `:#{attribute}_confirmation` instead of `attribute`.
569
-
570
- * Rails 4.0 has changed `ActiveModel::Serializers::JSON.include_root_in_json` default value to `false`. Now, Active Model Serializers and Active Record objects have the same default behaviour. This means that you can comment or remove the following option in the `config/initializers/wrap_parameters.rb` file:
571
-
572
- ```ruby
573
- # Disable root element in JSON by default.
574
- # ActiveSupport.on_load(:active_record) do
575
- # self.include_root_in_json = false
576
- # end
577
- ```
578
-
579
- ### Action Pack
580
-
581
- * Rails 4.0 introduces `ActiveSupport::KeyGenerator` and uses this as a base from which to generate and verify signed cookies (among other things). Existing signed cookies generated with Rails 3.x will be transparently upgraded if you leave your existing `secret_token` in place and add the new `secret_key_base`.
582
-
583
- ```ruby
584
- # config/initializers/secret_token.rb
585
- Myapp::Application.config.secret_token = 'existing secret token'
586
- Myapp::Application.config.secret_key_base = 'new secret key base'
587
- ```
588
-
589
- Please note that you should wait to set `secret_key_base` until you have 100% of your userbase on Rails 4.x and are reasonably sure you will not need to rollback to Rails 3.x. This is because cookies signed based on the new `secret_key_base` in Rails 4.x are not backwards compatible with Rails 3.x. You are free to leave your existing `secret_token` in place, not set the new `secret_key_base`, and ignore the deprecation warnings until you are reasonably sure that your upgrade is otherwise complete.
590
-
591
- If you are relying on the ability for external applications or Javascript to be able to read your Rails app's signed session cookies (or signed cookies in general) you should not set `secret_key_base` until you have decoupled these concerns.
592
-
593
- * Rails 4.0 encrypts the contents of cookie-based sessions if `secret_key_base` has been set. Rails 3.x signed, but did not encrypt, the contents of cookie-based session. Signed cookies are "secure" in that they are verified to have been generated by your app and are tamper-proof. However, the contents can be viewed by end users, and encrypting the contents eliminates this caveat/concern without a significant performance penalty.
594
-
595
- Please read [Pull Request #9978](https://github.com/rails/rails/pull/9978) for details on the move to encrypted session cookies.
596
-
597
- * Rails 4.0 removed the `ActionController::Base.asset_path` option. Use the assets pipeline feature.
598
-
599
- * Rails 4.0 has deprecated `ActionController::Base.page_cache_extension` option. Use `ActionController::Base.default_static_extension` instead.
600
-
601
- * Rails 4.0 has removed Action and Page caching from Action Pack. You will need to add the `actionpack-action_caching` gem in order to use `caches_action` and the `actionpack-page_caching` to use `caches_pages` in your controllers.
602
-
603
- * Rails 4.0 has removed the XML parameters parser. You will need to add the `actionpack-xml_parser` gem if you require this feature.
604
-
605
- * Rails 4.0 changes the default memcached client from `memcache-client` to `dalli`. To upgrade, simply add `gem 'dalli'` to your `Gemfile`.
606
-
607
- * Rails 4.0 deprecates the `dom_id` and `dom_class` methods in controllers (they are fine in views). You will need to include the `ActionView::RecordIdentifier` module in controllers requiring this feature.
608
-
609
- * Rails 4.0 deprecates the `:confirm` option for the `link_to` helper. You should
610
- instead rely on a data attribute (e.g. `data: { confirm: 'Are you sure?' }`).
611
- This deprecation also concerns the helpers based on this one (such as `link_to_if`
612
- or `link_to_unless`).
613
-
614
- * Rails 4.0 changed how `assert_generates`, `assert_recognizes`, and `assert_routing` work. Now all these assertions raise `Assertion` instead of `ActionController::RoutingError`.
615
-
616
- * Rails 4.0 raises an `ArgumentError` if clashing named routes are defined. This can be triggered by explicitly defined named routes or by the `resources` method. Here are two examples that clash with routes named `example_path`:
617
-
618
- ```ruby
619
- get 'one' => 'test#example', as: :example
620
- get 'two' => 'test#example', as: :example
621
- ```
622
-
623
- ```ruby
624
- resources :examples
625
- get 'clashing/:id' => 'test#example', as: :example
626
- ```
627
-
628
- In the first case, you can simply avoid using the same name for multiple
629
- routes. In the second, you can use the `only` or `except` options provided by
630
- the `resources` method to restrict the routes created as detailed in the
631
- [Routing Guide](routing.html#restricting-the-routes-created).
632
-
633
- * Rails 4.0 also changed the way unicode character routes are drawn. Now you can draw unicode character routes directly. If you already draw such routes, you must change them, for example:
634
-
635
- ```ruby
636
- get Rack::Utils.escape('こんにちは'), controller: 'welcome', action: 'index'
637
- ```
638
-
639
- becomes
640
-
641
- ```ruby
642
- get 'こんにちは', controller: 'welcome', action: 'index'
643
- ```
644
-
645
- * Rails 4.0 requires that routes using `match` must specify the request method. For example:
646
-
647
- ```ruby
648
- # Rails 3.x
649
- match '/' => 'root#index'
650
-
651
- # becomes
652
- match '/' => 'root#index', via: :get
653
-
654
- # or
655
- get '/' => 'root#index'
656
- ```
657
-
658
- * Rails 4.0 has removed `ActionDispatch::BestStandardsSupport` middleware, `<!DOCTYPE html>` already triggers standards mode per http://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx and ChromeFrame header has been moved to `config.action_dispatch.default_headers`.
659
-
660
- Remember you must also remove any references to the middleware from your application code, for example:
661
-
662
- ```ruby
663
- # Raise exception
664
- config.middleware.insert_before(Rack::Lock, ActionDispatch::BestStandardsSupport)
665
- ```
666
-
667
- Also check your environment settings for `config.action_dispatch.best_standards_support` and remove it if present.
668
-
669
- * In Rails 4.0, precompiling assets no longer automatically copies non-JS/CSS assets from `vendor/assets` and `lib/assets`. Rails application and engine developers should put these assets in `app/assets` or configure `config.assets.precompile`.
670
-
671
- * In Rails 4.0, `ActionController::UnknownFormat` is raised when the action doesn't handle the request format. By default, the exception is handled by responding with 406 Not Acceptable, but you can override that now. In Rails 3, 406 Not Acceptable was always returned. No overrides.
672
-
673
- * In Rails 4.0, a generic `ActionDispatch::ParamsParser::ParseError` exception is raised when `ParamsParser` fails to parse request params. You will want to rescue this exception instead of the low-level `MultiJson::DecodeError`, for example.
674
-
675
- * In Rails 4.0, `SCRIPT_NAME` is properly nested when engines are mounted on an app that's served from a URL prefix. You no longer have to set `default_url_options[:script_name]` to work around overwritten URL prefixes.
676
-
677
- * Rails 4.0 deprecated `ActionController::Integration` in favor of `ActionDispatch::Integration`.
678
- * Rails 4.0 deprecated `ActionController::IntegrationTest` in favor of `ActionDispatch::IntegrationTest`.
679
- * Rails 4.0 deprecated `ActionController::PerformanceTest` in favor of `ActionDispatch::PerformanceTest`.
680
- * Rails 4.0 deprecated `ActionController::AbstractRequest` in favor of `ActionDispatch::Request`.
681
- * Rails 4.0 deprecated `ActionController::Request` in favor of `ActionDispatch::Request`.
682
- * Rails 4.0 deprecated `ActionController::AbstractResponse` in favor of `ActionDispatch::Response`.
683
- * Rails 4.0 deprecated `ActionController::Response` in favor of `ActionDispatch::Response`.
684
- * Rails 4.0 deprecated `ActionController::Routing` in favor of `ActionDispatch::Routing`.
685
-
686
- ### Active Support
687
-
688
- Rails 4.0 removes the `j` alias for `ERB::Util#json_escape` since `j` is already used for `ActionView::Helpers::JavaScriptHelper#escape_javascript`.
689
-
690
- ### Helpers Loading Order
691
-
692
- The order in which helpers from more than one directory are loaded has changed in Rails 4.0. Previously, they were gathered and then sorted alphabetically. After upgrading to Rails 4.0, helpers will preserve the order of loaded directories and will be sorted alphabetically only within each directory. Unless you explicitly use the `helpers_path` parameter, this change will only impact the way of loading helpers from engines. If you rely on the ordering, you should check if correct methods are available after upgrade. If you would like to change the order in which engines are loaded, you can use `config.railties_order=` method.
693
-
694
- ### Active Record Observer and Action Controller Sweeper
695
-
696
- Active Record Observer and Action Controller Sweeper have been extracted to the `rails-observers` gem. You will need to add the `rails-observers` gem if you require these features.
697
-
698
- ### sprockets-rails
699
-
700
- * `assets:precompile:primary` and `assets:precompile:all` have been removed. Use `assets:precompile` instead.
701
- * The `config.assets.compress` option should be changed to `config.assets.js_compressor` like so for instance:
702
-
703
- ```ruby
704
- config.assets.js_compressor = :uglifier
705
- ```
706
-
707
- ### sass-rails
708
-
709
- * `asset-url` with two arguments is deprecated. For example: `asset-url("rails.png", image)` becomes `asset-url("rails.png")`.
710
-
711
- Upgrading from Rails 3.1 to Rails 3.2
712
- -------------------------------------
713
-
714
- If your application is currently on any version of Rails older than 3.1.x, you should upgrade to Rails 3.1 before attempting an update to Rails 3.2.
715
-
716
- The following changes are meant for upgrading your application to Rails 3.2.17,
717
- the last 3.2.x version of Rails.
718
-
719
- ### Gemfile
720
-
721
- Make the following changes to your `Gemfile`.
722
-
723
- ```ruby
724
- gem 'rails', '3.2.17'
725
-
726
- group :assets do
727
- gem 'sass-rails', '~> 3.2.6'
728
- gem 'coffee-rails', '~> 3.2.2'
729
- gem 'uglifier', '>= 1.0.3'
730
- end
731
- ```
732
-
733
- ### config/environments/development.rb
734
-
735
- There are a couple of new configuration settings that you should add to your development environment:
736
-
737
- ```ruby
738
- # Raise exception on mass assignment protection for Active Record models
739
- config.active_record.mass_assignment_sanitizer = :strict
740
-
741
- # Log the query plan for queries taking more than this (works
742
- # with SQLite, MySQL, and PostgreSQL)
743
- config.active_record.auto_explain_threshold_in_seconds = 0.5
744
- ```
745
-
746
- ### config/environments/test.rb
747
-
748
- The `mass_assignment_sanitizer` configuration setting should also be be added to `config/environments/test.rb`:
749
-
750
- ```ruby
751
- # Raise exception on mass assignment protection for Active Record models
752
- config.active_record.mass_assignment_sanitizer = :strict
753
- ```
754
-
755
- ### vendor/plugins
756
-
757
- Rails 3.2 deprecates `vendor/plugins` and Rails 4.0 will remove them completely. While it's not strictly necessary as part of a Rails 3.2 upgrade, you can start replacing any plugins by extracting them to gems and adding them to your Gemfile. If you choose not to make them gems, you can move them into, say, `lib/my_plugin/*` and add an appropriate initializer in `config/initializers/my_plugin.rb`.
758
-
759
- ### Active Record
760
-
761
- Option `:dependent => :restrict` has been removed from `belongs_to`. If you want to prevent deleting the object if there are any associated objects, you can set `:dependent => :destroy` and return `false` after checking for existence of association from any of the associated object's destroy callbacks.
762
-
763
- Upgrading from Rails 3.0 to Rails 3.1
764
- -------------------------------------
765
-
766
- If your application is currently on any version of Rails older than 3.0.x, you should upgrade to Rails 3.0 before attempting an update to Rails 3.1.
767
-
768
- The following changes are meant for upgrading your application to Rails 3.1.12, the last 3.1.x version of Rails.
769
-
770
- ### Gemfile
771
-
772
- Make the following changes to your `Gemfile`.
773
-
774
- ```ruby
775
- gem 'rails', '3.1.12'
776
- gem 'mysql2'
777
-
778
- # Needed for the new asset pipeline
779
- group :assets do
780
- gem 'sass-rails', '~> 3.1.7'
781
- gem 'coffee-rails', '~> 3.1.1'
782
- gem 'uglifier', '>= 1.0.3'
783
- end
784
-
785
- # jQuery is the default JavaScript library in Rails 3.1
786
- gem 'jquery-rails'
787
- ```
788
-
789
- ### config/application.rb
790
-
791
- The asset pipeline requires the following additions:
792
-
793
- ```ruby
794
- config.assets.enabled = true
795
- config.assets.version = '1.0'
796
- ```
797
-
798
- If your application is using an "/assets" route for a resource you may want change the prefix used for assets to avoid conflicts:
799
-
800
- ```ruby
801
- # Defaults to '/assets'
802
- config.assets.prefix = '/asset-files'
803
- ```
804
-
805
- ### config/environments/development.rb
806
-
807
- Remove the RJS setting `config.action_view.debug_rjs = true`.
808
-
809
- Add these settings if you enable the asset pipeline:
810
-
811
- ```ruby
812
- # Do not compress assets
813
- config.assets.compress = false
814
-
815
- # Expands the lines which load the assets
816
- config.assets.debug = true
817
- ```
818
-
819
- ### config/environments/production.rb
820
-
821
- Again, most of the changes below are for the asset pipeline. You can read more about these in the [Asset Pipeline](asset_pipeline.html) guide.
822
-
823
- ```ruby
824
- # Compress JavaScripts and CSS
825
- config.assets.compress = true
826
-
827
- # Don't fallback to assets pipeline if a precompiled asset is missed
828
- config.assets.compile = false
829
-
830
- # Generate digests for assets URLs
831
- config.assets.digest = true
832
-
833
- # Defaults to Rails.root.join("public/assets")
834
- # config.assets.manifest = YOUR_PATH
835
-
836
- # Precompile additional assets (application.js, application.css, and all non-JS/CSS are already added)
837
- # config.assets.precompile += %w( search.js )
838
-
839
- # Force all access to the app over SSL, use Strict-Transport-Security, and use secure cookies.
840
- # config.force_ssl = true
841
- ```
842
-
843
- ### config/environments/test.rb
844
-
845
- You can help test performance with these additions to your test environment:
846
-
847
- ```ruby
848
- # Configure static asset server for tests with Cache-Control for performance
849
- config.serve_static_assets = true
850
- config.static_cache_control = 'public, max-age=3600'
851
- ```
852
-
853
- ### config/initializers/wrap_parameters.rb
854
-
855
- Add this file with the following contents, if you wish to wrap parameters into a nested hash. This is on by default in new applications.
856
-
857
- ```ruby
858
- # Be sure to restart your server when you modify this file.
859
- # This file contains settings for ActionController::ParamsWrapper which
860
- # is enabled by default.
861
-
862
- # Enable parameter wrapping for JSON. You can disable this by setting :format to an empty array.
863
- ActiveSupport.on_load(:action_controller) do
864
- wrap_parameters format: [:json]
865
- end
866
-
867
- # Disable root element in JSON by default.
868
- ActiveSupport.on_load(:active_record) do
869
- self.include_root_in_json = false
870
- end
871
- ```
872
-
873
- ### config/initializers/session_store.rb
874
-
875
- You need to change your session key to something new, or remove all sessions:
876
-
877
- ```ruby
878
- # in config/initializers/session_store.rb
879
- AppName::Application.config.session_store :cookie_store, key: 'SOMETHINGNEW'
880
- ```
881
-
882
- or
883
-
884
- ```bash
885
- $ rake db:sessions:clear
886
- ```
887
-
888
- ### Remove :cache and :concat options in asset helpers references in views
889
-
890
- * With the Asset Pipeline the :cache and :concat options aren't used anymore, delete these options from your views.