It is exactly 1.9 compatible problem.
I have a similar issue with this:
http://www.ruby-forum.com/topic/168039
The variable rubygems_version is undefined on 1.9.
Thx again,
Huangxi
2010/3/12 Jim Gay j...@saturnflyer.com
I'm not sure of your exact problem, but Radiant is not 1.9.1 ready yet
hi all,
rake aborted when I run `rake production db:bootstrap`.
$rake production db:bootstrap --trace
(in /home/huangxi/develop/my_project)
rake aborted!
undefined method `=' for nil:NilClass
/home/huangxi/develop/my_project/config/boot.rb:138:in `load_rubygems'
I'm not sure of your exact problem, but Radiant is not 1.9.1 ready yet
On Fri, Mar 12, 2010 at 5:28 AM, Huang Xi huaihuaixiaos...@gmail.com wrote:
hi all,
rake aborted when I run `rake production db:bootstrap`.
$rake production db:bootstrap --trace
(in /home/huangxi/develop/my_project)
Hello
I am currently in the process of getting a cient's Radiant site that was
began earlier this year working locally on my machine, with the 0.8.1
version of Radiant.
I have hit an obstacle in the form of the error: undefined method
`output_buffer=' for ...
If anyone can help it would be
I have tried to run the radiant command on top of your existing project
replace the old configuration:
# radiant /www/radiant1
and got a message:
undefined method `camelize' for instance:String
Nevertheless request of the current version gave:
radiant -v
Hello again,
I just updated my system in order to try out the latest version of
Radiant and I am getting the following error in 0.7.1
NoMethodError (undefined method `fdiv' for 0:Fixnum):
/usr/lib/ruby/1.8/yaml/rubytypes.rb:146:in `is_binary_data?'
Radiant is not compatible with 1.8.7 because it is based on Rails
2.0.2. We'll upgrade to Rails 2.1.x soon.
Sean
Mark Kirby wrote:
hi,
I just updated my site to 0.6.7 gem and all was well. Then my system
updated ruby to ruby 1.8.7 (2008-06-20 patchlevel 22).
Now my front page just
It points to line 16 of the related_content/lib/related_content/
page_extensions.rb
I've pasted the trace below the previous emails.
Thanks for the help, Sean.
On Mar 22, 2008, at 12:56 PM, Sean Cribbs wrote:
Jim,
That's a stray artifact of something I did for Digital Pulp. Can
you give
Jim,
It seems that bug has been removed from the trunk version of the
extension, but the extension has not been updated for 0.6.5. You should
be safe to use it, but you might want to freeze the extension to the
current revision using Piston or something like that. We may be
updating the
