On Wed, Feb 14, 2018 at 9:24 AM, Roger van Schie
wrote:
>
> I think I will just extend the Page model to include a foreign key, and
> then add another check into the template tag to see whether the child page
> currently being "inspected" has a foreign key or not, and
Hi Ken
I might be missing your point, or misunderstanding something completely,
but templating is not a problem for me, I've written the models/templates
in such a way, that depending on what information they put into the page,
various parts of the page template get displayed or not, and hence
Hi Roger,
It is possible to do some terrifying things with the page templates. Read
http://mezzanine.jupo.org/docs/content-architecture.html#page-templates.
(Tortured language in that section is largely my fault, and improvements
are welcome.) I have managed to create "content inheritance trees"
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
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
Hi Roger. Would the Link model satisfy the requirements?
On Feb 8, 2018 5:48 AM, "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
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