# Problems with Radiant and vendor/gems load order

**URL:** <https://www.ruby-forum.com/t/problems-with-radiant-and-vendor-gems-load-order/197409>\
**Category:** Radiant CMS\
**Created:** [October 14, 2010, 12:40am UTC](https://www.ruby-forum.com/t/problems-with-radiant-and-vendor-gems-load-order/197409 "2010-10-14T00:40:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![okkezSS](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/85f322/32.png) [@okkezSS](https://www.ruby-forum.com/u/okkezSS)\
**Post date:** [October 14, 2010, 12:40am UTC](https://www.ruby-forum.com/t/problems-with-radiant-and-vendor-gems-load-order/197409/1 "2010-10-14T00:40:11Z")

</div>

All,

Rails 2.3.8  
Radiant 0.9.1 (vendored)  
Bundler 1.0.2

Yet another “this was just working, what the hell happened?”

My custom Radiant extension is dependent on a gem that I have in  
RAILS\_ROOT/vendor/gem. I can see that my extension is loading before  
the gem does and so that dependency is failing.

I am not sure how my load order got screwed up.

Do I just need to require my gem as usual in config/environment.rb or is  
there some Radiant specific way to make the gems be loaded first?

Thanks,  
Wes

---

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [October 14, 2010, 2:27am UTC](https://www.ruby-forum.com/t/problems-with-radiant-and-vendor-gems-load-order/197409/2 "2010-10-14T02:27:56Z")

</div>

On Wed, Oct 13, 2010 at 6:39 PM, Wes G. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> gem does and so that dependency is failing.
> 
> I am not sure how my load order got screwed up.
> 
> Do I just need to require my gem as usual in config/environment.rb or is  
> there some Radiant specific way to make the gems be loaded first?
> 
> Thanks,  
> Wes

Wes,  
Radiant bundles rails, so your version of rails should be irrelevant.  
What would be helpful is some sample code.  
Have you tried requiring the gem from within your extension?

---

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [October 14, 2010, 11:08pm UTC](https://www.ruby-forum.com/t/problems-with-radiant-and-vendor-gems-load-order/197409/3 "2010-10-14T23:08:16Z")

</div>

I have a similar problem.  
Jim, how do you require the gem from within the extension?

---

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [October 14, 2010, 11:17pm UTC](https://www.ruby-forum.com/t/problems-with-radiant-and-vendor-gems-load-order/197409/4 "2010-10-14T23:17:03Z")

</div>

require ‘whatever’ at the top of the extension file.

W

---

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [October 14, 2010, 11:43pm UTC](https://www.ruby-forum.com/t/problems-with-radiant-and-vendor-gems-load-order/197409/5 "2010-10-14T23:43:53Z")

</div>

i actually had a different problem (my gem folder was empty!) sorry  
for the unnecessary email

---

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [October 14, 2010, 11:22pm UTC](https://www.ruby-forum.com/t/problems-with-radiant-and-vendor-gems-load-order/197409/6 "2010-10-14T23:22:03Z")

</div>

On 10/13/10 7:26 PM, Jim G. wrote:

> > RAILS\_ROOT/vendor/gem. I can see that my extension is loading before the  
> > Wes,  
> > Radiant bundles rails, so your version of rails should be irrelevant.  
> > What would be helpful is some sample code.  
> > Have you tried requiring the gem from within your extension?  
> > This was a problem that I had with Devise and assumptions that it makes  
> > when defining helper methods for inclusion into controllers.

I’ll provide more detail later.

W