# After 1.2 upgrade - a copy of X has been removed from the mo

**URL:** <https://www.ruby-forum.com/t/after-1-2-upgrade-a-copy-of-x-has-been-removed-from-the-mo/107284>\
**Category:** Rails\
**Created:** [June 20, 2007, 3:37am UTC](https://www.ruby-forum.com/t/after-1-2-upgrade-a-copy-of-x-has-been-removed-from-the-mo/107284 "2007-06-20T03:37:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_L\_Bean](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f05b48/32.png) [@David\_L\_Bean](https://www.ruby-forum.com/u/David_L_Bean)\
**Post date:** [June 20, 2007, 3:37am UTC](https://www.ruby-forum.com/t/after-1-2-upgrade-a-copy-of-x-has-been-removed-from-the-mo/107284/1 "2007-06-20T03:37:19Z")

</div>

All,

I’ve been diligently looking for a complete answer to the following  
question, but I haven’t seen any real resolution to it. Anyone have  
any new news?

Problem: After associating an authentication method of the  
Application controller with before\_filter throughout the application,  
I will occasionally get this error:

A copy of ApplicationController has been removed from the module tree  
but is still active!

This did not happen prior to my upgrade to 1.2.

The workaround I’m using is to force Rails not to dynamically load/  
unload the app’s controllers, i.e. in environment.rb:

## chasing update to 1.2 error…

config.load\_once\_paths += %W{ #{RAILS\_ROOT}/app/controllers }

That keeps the error at bay, but I have to restart the server anytime  
I make a change during development, which is a royal pain in the  
patootie and something that negates one of the best characteristics of  
Rails.

Thanks for any help,

- David