What have you tried? Django should create the migration when you swap
out the subclasses. It's mostly going to remove fields since Page is a
subclass of Displayable anyways.
There's also the nuclear option of just migrating your app back to zero
to delete the tables and just create a new
Is there a way to migrate from Page to Displayable?
I have tried and it seems to be a pain...
--
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
Eduardo I have seen the video of your explanation and it is exactly the
solution for me, thank you very much.
In my opinion, for the beginners like me, would be of more help if the
Mezzanine documentation were more explicit, with more examples.
Now that I have lived through this experience I can
When I develop a Mezzanine site, there's usually two types of models I use:
1. Custom Page types. These are models that users want to incorporate
into the page menu, and they must be editable/orderable from the page
tree in the admin. In this case the model must inherit from
Yes, I've illustrated above, if I do it like in Django Polls Tutorial, just
admin.site.register (Ingredient)
the listing will be ok, but in this case, the rendering of creating/editing
page isn't convenient, considering the number of fields that need to be
filled. For the creating/editing page
Why not just have Ingredients as a normal Django model (not inheriting from
Page). Similar to the Blog, or the Django Polls Tutorial?
On Thu, Sep 14, 2017 at 12:12 PM, Rainell Dilou Gómez <
rainell.di...@gmail.com> wrote:
> Hello,
> I have created a custom content type and I have a problem with
