Hmmm... basically you're talking about subclassing routes, or at least
aliasing them (so that myusertype_photo_url is the same as user_photo_url).
Looks like there's a ticket (http://dev.rubyonrails.org/ticket/10454) with
some ideas on how to fix it. In particular, you could override the
The following stack trace
NoMethodError (undefined method `my_user_type_photo_url' for
#UserNotifier:0x3cbd560):
/Library/Ruby/Gems/1.8/gems/actionpack-2.2.2/lib/action_controller/
polymorphic_routes.rb:112:in `__send__'
/Library/Ruby/Gems/1.8/gems/actionpack-2.2.2/lib/action_controller/
This is probably not the best way to do it, but I ended up copying and
pasting all the routes for User for each of my subclassed user types.
On Mar 31, 1:39 pm, moritz a5s...@yahoo.com wrote:
I've subclassed the CE User type using single-table inheritance and it
all seemed to work fine.
Now
