Hello Jacob,
I see that what I need require a lot of knowledge about how Django-CMS work
at the javascript frontend level and I'm not there yet.
I found a quick work around.
My descendant child plugin has a list of ancestors that it can be included
in and I get all the parents class name and
Hello,
the parent/child based restriction for plugins is a bit too much
restrictive for my use case.
I have a suggestion but I'm not sure how to implement it. I'd like some
guidance on what to modify to achieve what I want.
The idea is to have a required_ancestor to some plugins.
For example
