Just an update with some more details: Tried extending the Displayable model to create a lower level custom model with one ImageField and three CharFields, and registering with DisplayableAdmin, but behavior wasn't as expected -- the model appeared with the custom name, but the fields were the same as the existing BlogPost model. I also just discovered this gist <https://gist.github.com/kenbolton/5885243> for creating a custom page admin to register the model, would this be frowned upon?
On Monday, June 26, 2017 at 11:57:55 PM UTC-7, [email protected] wrote: > > Hi, I have a few custom models that are built off of the Page model and > manager, and work great. But there is one model where it would be useful > for an inherited field (Show in Navigation booleans) to either set to > editable=false or remove them entirely. Is this possible? > > I'm worried that the fact the default states are all True and the extra > interaction required will effect the experience. I have read many posts on > the mailing list, stack overflow, and the git issues usually suggesting > that this is not a good idea and can cause unforeseen breakage, but the > Show in Nav bools seem pretty innocuous. I was thinking maybe finding a way > to hack some javascript into the admin to check the url and hide the fields > conditionally, but there must be a better way. If you have any ideas, I'm > open to anything! Thanks for a great tool! > -- 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.
