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 compare. If the required ancestor is found, I set a variable in the context to true and the template render the plugin. If the required ancestor is *not* found, I set a variable in the context to false and the template render the plugin with an error message that list the required ancestors. Frédéric Le jeudi 23 janvier 2020 23:02:07 UTC+1, Jacob Rief a écrit : > > Hello Frédéric, > this is something I always wanted to implement, because it makes the > configuration of plugins unnecessarily difficult. > Please read this proposal: https://github.com/divio/django-cms/issues/6110 > > If you wonder, why I never implemented it: no spare time/lack of funding. > > Best Regards, > Jacob > > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to [email protected] --- You received this message because you are subscribed to the Google Groups "django CMS developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/f0fc15fd-2c5b-47c8-b82c-53f3e7ab4c30%40googlegroups.com.
