Re: Using Model name in the url

2009-03-12 Thread Jacob Kaplan-Moss
On Tue, Mar 10, 2009 at 9:44 PM, Michael Strickland wrote: > So I've actually run into a new problem: declaring the permalink for > only the inherited models works fine, but whenever I query the > database using the base model's manager (so I can get results from all > of the inherited models), t

Re: Using Model name in the url

2009-03-10 Thread Michael Strickland
So I've actually run into a new problem: declaring the permalink for only the inherited models works fine, but whenever I query the database using the base model's manager (so I can get results from all of the inherited models), the resulting objects that are returned use the base model's permalin

Re: Using Model name in the url

2009-03-10 Thread Michael Strickland
It seems to be working now... I can't say what went wrong, however - the legacy code I copied over looked exactly the same as the current code :/. But thanks! -Michael On Mar 10, 8:44 pm, Alex Gaynor wrote: > On Tue, Mar 10, 2009 at 7:40 PM, Michael Strickland > wrote: > > > > > > > I currentl

Re: Using Model name in the url

2009-03-10 Thread Alex Gaynor
On Tue, Mar 10, 2009 at 7:40 PM, Michael Strickland wrote: > > I currently have a base model called Content, with models such as > Article, Image, and Video subclassing Content. Currently, > get_absolute_url works only when it is located in Content - if I try > placing get_absolute_url in any of t

Using Model name in the url

2009-03-10 Thread Michael Strickland
I currently have a base model called Content, with models such as Article, Image, and Video subclassing Content. Currently, get_absolute_url works only when it is located in Content - if I try placing get_absolute_url in any of the inherited models, instead of the base model, it returns an empty s