#320 √ resolved
Jon Buda

BlueCloth, markdown(), config.gem, unpack gem and Rails 2.1 not working properly?

Reported by Jon Buda | June 3rd, 2008 @ 06:36 PM

I've been using Edge Rails for awhile and 2.1 as of today and I've noticed something really weird going on with the BlueCloth gem while trying to unpack it into the vendor/gems dir using the new gem dependency stuff in 2.1 so that I can deploy my app without having to install the BlueCloth gem.

For easy of deployment, I'm trying to vendor all my gems. So I install the BlueCloth gem locally, then in my environment.rb I have the line: 

config.gem 'BlueCloth', :lib => "bluecloth", :version => '1.0.0'

Simple enough. Then I do 'rake gems:unpack:dependencies' to unpack BlueCloth into 'vendor/gems/BlueCloth-1.0.0'. Seems to work fine. Now if I uninstall the local gem 'sudo gem uninstall BlueCloth' and run my rails app, the 'markdown()' helper method is no longer found. So in my views, this no longer works: 

<%= markdown sometext.body %>

However, this does work in my views: 

<%= BlueCloth::new(sometext.body).to_html %>

So I know the gem is being loaded from the vendor/gems dir. Is this a bug in the Rails code or am I doing something wrong here?

I've looked at the source code (line 253 in text_helper.rb) for the 'markdown' helper and it contains the line: 

require_library_or_gem "bluecloth" unless Object.const_defined?(:BlueCloth)

After which it defines the 'markdown()' which apparently isn't being defined in my case...

If I try 'Object.const_defined?(:BlueCloth)' from script/console it returns true

Is text_helper.rb trying to define the markdown method before the gem is loaded from vendor/gems?

Comments and changes to this ticket

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

Creating or reviewing a patch

See the contributor guide.

Creating a feature request

Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.

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".

Shared Ticket Bins

People watching this ticket