From d3223b5b65c50e675da3f5d4726a5baa0d9f2010 Mon Sep 17 00:00:00 2001 From: adman65 Date: Thu, 22 Mar 2012 12:10:52 +0100 Subject: Update config.assets.initialize_on_precompile warning to include engine side affects --- guides/source/asset_pipeline.textile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/guides/source/asset_pipeline.textile b/guides/source/asset_pipeline.textile index b1b1d21c2d..a1b7a42d66 100644 --- a/guides/source/asset_pipeline.textile +++ b/guides/source/asset_pipeline.textile @@ -409,7 +409,9 @@ cannot see application objects or methods. *Heroku requires this to be false.* WARNING: If you set +config.assets.initialize_on_precompile+ to false, be sure to test +rake assets:precompile+ locally before deploying. It may expose bugs where your assets reference application objects or methods, since those are still -in scope in development mode regardless of the value of this flag. +in scope in development mode regardless of the value of this flag. Changing this flag also effects +engines. Engines can define assets for precompilation as well. Since the complete environment is not loaded, +engines (or other gems) will not be loaded which can cause missing assets. Capistrano (v2.8.0 and above) includes a recipe to handle this in deployment. Add the following line to +Capfile+: -- cgit v1.2.3