Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

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

#320

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?

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

State: resolved
Milestone: none
Assigned to: Rick Rick
Importance: none

Activity

  1. DHH
    DHH
    • Assigned user set to Rick

    June 3rd, 2008 @ 06:39 PM

  2. Rick
    Rick
    • State changed from new to verified

    I simply modified the rails initializer so that the gem load paths are added before the rails framework is loaded. This should solve the issue. Please try with my rails fork and let me know if it works for you.

    June 8th, 2008 @ 07:31 PM

  3. Jon Buda
    Jon Buda

    Rick,

    Looks like that did the trick. Thanks for looking into it. This should find its way into the next stable release?

    June 9th, 2008 @ 04:23 PM

  4. Repository
    Repository
    • State changed from verified to resolved

    (from [51e4106dcc58e5218e8b297ad870a063b7bb1ab8]) Add the gem load paths before the framework is loaded, so certain gems like RedCloth and BlueCloth can be frozen. [#320 state:resolved]

    http://github.com/rails/rails/co...

    June 19th, 2008 @ 06:01 PM

  5. Repository
    Repository

    (from [924244bf5cfb3d359fbc58d935d33adebf571fd6]) Add the gem load paths before the framework is loaded, so certain gems like RedCloth and BlueCloth can be frozen. [#320 state:resolved]

    http://github.com/rails/rails/co...

    June 19th, 2008 @ 06:12 PM

  6. Aditya Sanghi
    Aditya Sanghi

    Automatic cleanup of spam.

    October 12th, 2010 @ 10:16 AM

  7. Ryan Bigg
    Ryan Bigg

    Automatic cleanup of spam.

    October 13th, 2010 @ 06:25 AM