# Acts\_as\_taggable (the gem) woes (solved)

**URL:** <https://www.ruby-forum.com/t/acts-as-taggable-the-gem-woes-solved/82716>\
**Category:** Ruby\
**Created:** [January 19, 2007, 11:20pm UTC](https://www.ruby-forum.com/t/acts-as-taggable-the-gem-woes-solved/82716 "2007-01-19T23:20:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jean\_l](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/82dd89/32.png) [@jean\_l](https://www.ruby-forum.com/u/jean_l)\
**Post date:** [January 19, 2007, 11:20pm UTC](https://www.ruby-forum.com/t/acts-as-taggable-the-gem-woes-solved/82716/1 "2007-01-19T23:20:17Z")

</div>

Hi,

I had to battle quite a bit to find how to load acts\_as\_taggable  
without using require\_gem.

where I previously had

require\_gem ‘acts\_as\_taggable’

I tried replacing by the obvious

gem ‘acts\_as\_taggable’  
require ‘acts\_as\_taggable’

this failed miserably. The trick is that the acts\_as\_taggable module  
is in a file named taggable in the lib directory of the gem. so to get  
it to work you have to replace the require with :

require ‘taggable’

Now you can use acts\_as\_taggable without any warnings. While this may  
seem obvious to many here, I hope it prevents the waste of a couple  
hours to a few other newbies thus my post.

Back to tracking every last of these deprecation warnings now that my  
test pass again 🙂

Jean

---

<div class="post-metadata">

**Author:** ![jean\_l](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/82dd89/32.png) [@jean\_l](https://www.ruby-forum.com/u/jean_l)\
**Post date:** [January 19, 2007, 11:47pm UTC](https://www.ruby-forum.com/t/acts-as-taggable-the-gem-woes-solved/82716/2 "2007-01-19T23:47:20Z")

</div>

Dammit!  
I posted to the wrong list.  
Sorry about that