Joel,
A fix will be pushed soon. A few people ran into that this afternoon in
the IRC channel while I was hacking on a few things.
Sean
Joel Oliveira wrote:
Hi everyone -
I understand freezing to Radian't edge will vary one's experience since it's
under active development, obviously. Just thought I'd throw this out in
case anyone has run into this yet.
I froze it per the instructions at the radiant site, and upon subsequent
rake tasks, I got an error
rake aborted!
wrong number of arguments (0 for 1)
...
/vendor/radiant/lib/tasks/rspec.rake:197:in `t'
the culprit being :
namespace :generators do
[:extension_controller, :extension_mailer, :extension_migration,
:extension_model, :extension].each do |generator|
* task t => :spec_prereq*
end
end
---
I commented it out for the time being to continue some tests (the commenting
successfully staved that off), and the first time I fired up script/server
joel$ script/server
=> Booting Mongrel
=> Rails 2.3.2 application starting on http://0.0.0.0:3000
/Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/actionpack/lib/action_controller/vendor/rack-1.0/rack.rb:17:
warning: already initialized constant VERSION
/Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/activesupport/lib/active_support/dependencies.rb:105:in`const_missing':
uninitialized constant Rails::Initializer::ResponseCache
(NameError)
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/config/environments/development.rb:15:in `load_environment'
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/railties/lib/initializer.rb:365:in`load_environment'
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/activesupport/lib/active_support/core_ext/kernel/reporting.rb:11:in`silence_warnings'
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/railties/lib/initializer.rb:358:in`load_environment'
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/railties/lib/initializer.rb:137:in`process'
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/railties/lib/initializer.rb:113:in`send'
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/railties/lib/initializer.rb:113:in`run'
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/lib/radiant/initializer.rb:111:in `run'
... 6 levels...
from /Users/joel/Documents/Projects/Rails/
radiant_jo.com/vendor/radiant/vendor/rails/railties/lib/commands/server.rb:84
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
`require'
from script/server:3
Again - commenting that out in environments/development.rb held off that
issue.
Would this have something to do with the recent efforts to move Radiant to
Rails 2.3?
Lastly - love Radiant. Finally something flexible enough to bend to our
will, while not dealing with heaps and mounds of extraneous and unnecessary
"features"
- Joel
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
