cache_classes should be true by default
Reported by Damian Janowski | July 17th, 2008 @ 12:24 PM | in 2.2
Rails is assuming a "development mode"-like behavior. It seems that this is actually the exception -- ie not more than a "goodie" for developing.
This should not affect anybody in a bad way. Worst case scenario is that this will actually fix things on misconfigured servers (or in cases where you define your custom environment but don't have a config/environments/custom.rb -- by default Rails should assume that is not another development environment).
Comments and changes to this ticket
-
-
-
Jeremy Kemper July 30th, 2008 @ 03:57 AM
- → State changed from “new” to “open”
- → Assigned user changed from “” to “Joshua Peek”
- → Milestone changed from “2.x” to “2.2”
-
Joshua Peek July 31st, 2008 @ 01:31 PM
Fair enough since "config.cache_classes = false" is the default for everyone's generated development environments.
-
Repository July 31st, 2008 @ 01:43 PM
- → State changed from “open” to “resolved”
(from [030d5854adcf35e6620d667a93a922f5d91725d8]) Turn cache_classes on by default [#645 state:resolved]
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
