So I have a routing problem I'm running into.
I have a model called Film, and each Film belongs to categories, which
are being store in the DB as a serialized array in the category column.
The films_controller is working right now with index, new, edit, delete
actions. All is well using the default rails routing scheme.
What I want to do is keep the films_controller as close to as it is now,
but allow the user to view films by category using a url like this
without loosing the ability to manage all films using urls like this:
I've tried setting up a route like this, both before and after the
default rails routes:
map.admin_films 'admin/films/:category/:action/:id', :controller =>
When I place it before the default rails routes I get the category pages
working, but the global actions (/admin/films/edit/1) error out with the
'No action responded to 1'
When I place it after the default rails routes the category pages don't
work and I get the following error:
'No action responded to narrative_features'
(narrative_features being on of the categories films can belong to)
Any help is appreciated.