It is possible to do some terrifying things with the page templates. Read
(Tortured language in that section is largely my fault, and improvements
are welcome.) I have managed to create "content inheritance trees" across
`Displayable`s by (ab)using the Mezzanine page templates.
A note of caution: a lot of folks think their content and architecture is
unique, a special butterfly that doesn't fit long-established information
architecture patterns. I have yet to find a case where that is true, though
I acknowledge your client may have found it. Often, it only takes careful
management by engineering to help the customer past this.
On Wed, Feb 14, 2018 at 3:47 AM, Roger van Schie <roger.vansc...@gmail.com>
> Hi Everyone
> As far as I can tell, the "Link" page won't work for me because I pull
> information from the child page to display in the parent page. Basically,
> my client has different categories, and within those categories they have
> sub-categories, and so on, all built using the page tree structure. The
> sub-categories are displayed on the category page on a "card", with an
> image that is pulled from the sub-category page. I've basically created a
> custom menu, where the child pages' display more than just the title.
> Would an appropriate approach be to extend the link model to include a
> foreign key linking to the actual page? Or should I just extend the Page
> model with a foreign key to point to the other page? Anyone got a better
> suggestion / solution?
> On 8 February 2018 at 22:34, Danny <molo...@gmail.com> wrote:
>> On 8/02/2018 9:18 PM, Roger van Schie wrote:
>>> Hi Everyone
>>> I have a use case where the client basically wants a rich text field
>>> page to write about a certain product, but this product falls under
>>> different categories. Each category is higher up in the branch hierarchy,
>>> and they want that same page(the rich text field page) to be displayed in
>>> multiple categories.
>>> My current thinking is to just create a custom page model that has a
>>> foreign key to the other page and put that in the page tree. Would this be
>>> the best approach?
>> An easier way to do it is to have the actual page at one place in the
>> hierarchy, and then use a 'Link' page elsewhere to automatically go to this
>> page. I've done this before, no troubles.
>> It will mean that when viewing the page it will always just have the one
>> breadcrumb trail, but it will still be available from two places within the
>> navigation menus.
>> Seeya. Dnany.
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
> 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
For more options, visit https://groups.google.com/d/optout.