Using nested controllers

Question

Since my site had an admin section and a normal (front-end user) section, I needed to structure the articles controller in such a way that it was RESTful.

So what I did was , have 2 articles controllers, 1 nested under the admin namespace (which would result in admin/articles) and the other one as a normal articles resource (/articles). (I followed this blog.)

Now I started facing issues such as

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

2 questions .

Is this error really because of me using such a structure of nested resources?
Is it a good programming practice to use such a structure? If not, is there a better alternative?

Thanks!

Pan Thomakos · Accepted Answer · 2010-12-18 19:41:54Z

2

The structure is perfectly fine, and your code will probably function just fine in production mode. The issue usually arises in development when modules or classes are not 'unloaded' after a first request. Without seeing the code it's hard to tell exactly which module or plugin might be causing this issue, but you might want to have a look at this blog post.

You can usually solve this issue by loading the offending module or class only once:

config.autoload_once_paths << '/path/to/class/or/module.rb'

or by reloading your plugins in development mode:

config.reload_plugins = true if Rails.env == 'development'

answered Dec 18, 2010 at 19:41

Pan Thomakos

34.4k9 gold badges90 silver badges86 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Using nested controllers

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related