Hi Rich, Your converted model, let's call it `Author`, will have all the fields from your legacy Django app, e.g. `dob` for "date of birth". The database table for the `Author` model, `myapp_author`, contains fields `page_ptr_id` and `dob`. `page_ptr_id` will hold the primary-key to the parent `Page`, db table `pages_page`.
The `Page` object should be created when the `Author` is created. If you have existing `Author`s, you can script the creation of a `Page` object for each `Author`. Sometimes, the thing you want to display doesn't belong in a page hierarchy. I find it sometimes useful to sub-class `Displayable`. For posterity, this is the relevant section of the docs: http://mezzanine.jupo.org/docs/content-architecture.html#creating-custom-content-types -ken On Sun, Mar 12, 2017 at 11:59 AM, Richard Jackson <[email protected]> wrote: > Hi there, > > I'm converting a Django app to work within a Mezzanine site. Within > "models.py", when I change the inherited class from "models.Model" to > "Page" I'm asked to give a value for non-nullable 'page_ptr' - what should > this be? > > Thanks for any help with this, > > Rich > > -- > 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. > -- 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.
