# Using depreciated methods & things moved to plugins (ex. act\_as\_tree)

**URL:** <https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772>\
**Category:** Rails\
**Created:** [January 11, 2008, 10:27pm UTC](https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772 "2008-01-11T22:27:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![melvinram](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@melvinram](https://www.ruby-forum.com/u/melvinram)\
**Post date:** [January 11, 2008, 10:27pm UTC](https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772/1 "2008-01-11T22:27:05Z")

</div>

As a Rails newbie, I am not sure how to feel about methods that have  
been moved into plugins. Why are they moved into plugins in the first  
place? Should I use the plugin if it wasn’t good enough to keep in the  
core code?

---

<div class="post-metadata">

**Author:** ![melvinram](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@melvinram](https://www.ruby-forum.com/u/melvinram)\
**Post date:** [January 11, 2008, 10:29pm UTC](https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772/2 "2008-01-11T22:29:25Z")

</div>

It was moved out of the core because the functionality is not core  
functionality. The plugins (acts\_as\_list / acts\_as\_tree) are the same,  
and  
just as supported. It’s all about consistency, that code fits better as  
plugins.

Jason

---

<div class="post-metadata">

**Author:** ![melvinram](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@melvinram](https://www.ruby-forum.com/u/melvinram)\
**Post date:** [January 11, 2008, 10:36pm UTC](https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772/3 "2008-01-11T22:36:34Z")

</div>

So using code that has been moved out from rails into plugins is not a  
bad idea? I’m afraid of learning how to use them and building apps w/  
them and later find out that there is a better way to do it and that  
is why it was removed in the first place.

---

<div class="post-metadata">

**Author:** ![melvinram](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@melvinram](https://www.ruby-forum.com/u/melvinram)\
**Post date:** [January 12, 2008, 2:24pm UTC](https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772/4 "2008-01-12T14:24:14Z")

</div>

That being said, I would be really hesitant to use the “classic”  
pagination  
plugin instead of the recommended will\_paginate [or it’s less  
appreciated  
but equally awesome sister paginating\_find]. There’s a reason pagination  
was  
taken out of Rails core based on inefficiency.

RSL

---

<div class="post-metadata">

**Author:** ![melvinram](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@melvinram](https://www.ruby-forum.com/u/melvinram)\
**Post date:** [January 11, 2008, 10:54pm UTC](https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772/5 "2008-01-11T22:54:45Z")

</div>

Well, the concern you’ve got here is slightly different. Unfortunately  
with  
software, this happens all the time, and Rails is a constantly evolving  
library. Something that might be The Way (aka REST right now), may in a  
few  
months time be replaced with something better. You can’t be afraid of  
this  
or you’ll never get any work done. Work with what’s available now, and  
as  
things change you can move with the changes or you can stay with the  
older  
versions, which will still work.

Jason

---

<div class="post-metadata">

**Author:** ![melvinram](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@melvinram](https://www.ruby-forum.com/u/melvinram)\
**Post date:** [January 13, 2008, 1:25pm UTC](https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772/6 "2008-01-13T13:25:19Z")

</div>

The classic pagination is the only one off hand that I can think of that  
was  
specifically deprecated because Rails core found it to be suboptimal.  
IIRC  
the others were moved to plugins because they were deemed to be  
peripheral  
functionality. Someone please correct me if I’m wrong there. 🙂

RSL

---

<div class="post-metadata">

**Author:** ![melvinram](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a698b9/32.png) [@melvinram](https://www.ruby-forum.com/u/melvinram)\
**Post date:** [January 13, 2008, 2:34am UTC](https://www.ruby-forum.com/t/using-depreciated-methods-things-moved-to-plugins-ex-act-as-tree/125772/7 "2008-01-13T02:34:16Z")

</div>

Are there other plugins you would recommend staying away from?

~ mel
