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
mezzanine.pages.models.Page and the admin class must inherit from
mezzanine.pages.admin.PageAdmin.
2. Displayable models. These are models we don't want to incorporate
into the page menu, we want them to have their own section in the public
site and their own list-enabled admin interface. The prime example is
Mezzanine's built-in blog. It has it's own admin and it's own urls to
display the BlogPost list and detail views. In this case the model must
inherit from mezzanine.core.models.Displayable and the admin class from
mezzanine.core.admin.DisplayableAdmin.
It looks to me like you want to go with approach #2. I suggest you
re-write your models to use the Displayable base model and admin.
I gave a talk last year regarding this topic at DjangoCon. It explains
how to convert a normal Django app into a Displayable-based Mezzanine
app. Hopefully it'll be useful: https://www.youtube.com/watch?v=yVAmMXES2EU
On 2017-09-14 9:36 AM, Joseph Mohan wrote:
Yes, i've ran into this sort of thing a few times and not been able to
figure an easy way so I try to use non-Page models..
A solution that I have used is to create a custom admin page and show
a list of your custom pages. Not an elegant solution at all.
I'm really interested to see if ayone else ever deals with this!
On Thu, Sep 14, 2017 at 2:10 PM, Rainell Dilou Gómez
<[email protected] <mailto:[email protected]>> wrote:
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 would
be much more convenient to obtain a result equal to that obtained
using PageAdmin.
The most convenient result would be a simple listing (see third
image), which we can obtain following the example of Django Polls
Tutorial ( just admin.site.register(Ingredient) ) and an
creat/edit page as the one we can obtain using PageAdmin (
dmin.site.register(Ingredient, PageAdmin). See first image ). But
how to do it?
Il giorno giovedì 14 settembre 2017 13:12:56 UTC+2, Rainell Dilou
Gómez ha scritto:
Hello,
I have created a custom content type and I have a problem with
the listing in the admin panel. If I extends PageAdmin
|
admin.site.register(Ingredient,PageAdmin)
|
the create/edit page is rendered as in the image
<https://lh3.googleusercontent.com/-Ohd3o8QKwmg/WbpcWgjV5fI/AAAAAAAAAdc/i_yp_ntXQEcTMcfB8-5yFBsySLINt11sgCLcBGAs/s1600/Schermata%2B2017-09-14%2Balle%2B12.26.00.png>
and this is great for creating and editing, but the listing in
the page section, as show in the following image, is a problem
because the Ingredients (my custom content type) will be many,
will be hundreds.
<https://lh3.googleusercontent.com/-Yap3P0bVjw0/WbpbLnHhsMI/AAAAAAAAAdQ/HGkHjriVlRIMgb1qoH7OMxusCZQdvoEeACLcBGAs/s1600/Schermata%2B2017-09-14%2Balle%2B12.24.32.png>
If instead I don't extend PageAdmin
|
admin.site.register(Ingredient)
|
my custom content type list is rendered as in the following
image, in a more convenient way, considering that there will
be hundreds of Ingredients
<https://lh3.googleusercontent.com/-ehaJO4GKoHs/WbpfH1qDOFI/AAAAAAAAAdo/I2BKgYN5jyUADxoBgDpNIgJ3jM13JD0tACLcBGAs/s1600/Schermata%2B2017-09-14%2Balle%2B12.27.13.png>
but the create/edit page will be rendered as in the next
image, and it isn't convenient, considering that the fields
are twice as many as are shown in this image.
<https://lh3.googleusercontent.com/-eT-u4auTnCU/WbphFcKL65I/AAAAAAAAAd8/ZO51pAVa3SsThgkUJSPJs0OTGs_NZatIQCLcBGAs/s1600/Schermata%2B2017-09-14%2Balle%2B12.27.38.png>
So how can I do to create/edit as when using PageAdmin and
list as when not using PageAdmin?
--
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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout
<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]
<mailto:[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.
