Hello, in the documentation there's no mention that I've found so far about extending existing models with a Page variant. The Author example creates a model that is also a Page. A different approach is to create an AuthorPage as:
class AuthorPage(Author, Page) and doing it like this gives an error message on validate and any operation that calls validate: "ordering" refers to "_order", a field that doesn't exist. The apparent solution is to swap Page and Author, but are there other caveats? Is there a reason not to do it like this? The reason I prefer to do it like this, is that I don't have to refactor my or 3rd party applications in order to make them useful within Mezzanine. The method using URL patterns doesn't appeal to me, cause I expect I still have to deal with views and resulting site inconsistencies. -- Melvyn Sopacua -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
