When using bluecloth and the ruby-lsapi 2.0 BlueCloth throws an error about not being able to convert LSAPI to a string.
Here is the error
can't convert LSAPI into String
RAILS_ROOT: /Users/tdinkins/dev/test/config/..
Application Trace | Framework Trace | Full Trace
/usr/local/lib/ruby/1.8/logger.rb:526:in `exist?'
/usr/local/lib/ruby/1.8/logger.rb:526:in `open_logfile'
/usr/local/lib/ruby/1.8/logger.rb:496:in `initialize'
/usr/local/lib/ruby/1.8/logger.rb:272:in `initialize'
/usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:127:in `initialize'
#{RAILS_ROOT}/app/controllers/users_controller.rb:17:in `show'
/usr/local/lsws/fcgi-bin/RailsRunner.rb:14
I have track the error to line 127 in lib/bluecloth.rb. It is using the global variable $deferr, which is LSAPI (I am not sure what that is at this point).
If I replace Logger with a dummy class that doesn't do anything but eat what is passed to it, all is well. So I know it is definitely the passing of $deferr to the logger that blows it up.
Also, ruby-lsapi version 1.13 does not have this problem.
I have tested this in 2 rails blogging apps, and recently a new test app with nothing in it but a scaffold for a simple model with 2 fields.
I am attaching an app that will produce the problem.
Also of note, I am using rails 1.2 and rails 1.1.6, on different systems, with the same results.
Here is the error
can't convert LSAPI into String
RAILS_ROOT: /Users/tdinkins/dev/test/config/..
Application Trace | Framework Trace | Full Trace
/usr/local/lib/ruby/1.8/logger.rb:526:in `exist?'
/usr/local/lib/ruby/1.8/logger.rb:526:in `open_logfile'
/usr/local/lib/ruby/1.8/logger.rb:496:in `initialize'
/usr/local/lib/ruby/1.8/logger.rb:272:in `initialize'
/usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.0/lib/bluecloth.rb:127:in `initialize'
#{RAILS_ROOT}/app/controllers/users_controller.rb:17:in `show'
/usr/local/lsws/fcgi-bin/RailsRunner.rb:14
I have track the error to line 127 in lib/bluecloth.rb. It is using the global variable $deferr, which is LSAPI (I am not sure what that is at this point).
If I replace Logger with a dummy class that doesn't do anything but eat what is passed to it, all is well. So I know it is definitely the passing of $deferr to the logger that blows it up.
Also, ruby-lsapi version 1.13 does not have this problem.
I have tested this in 2 rails blogging apps, and recently a new test app with nothing in it but a scaffold for a simple model with 2 fields.
I am attaching an app that will produce the problem.
Also of note, I am using rails 1.2 and rails 1.1.6, on different systems, with the same results.