I like the proposal. And it seems it can be implemented on top of existing code - even by an almost standalone plugin.
It has to be able to: 1. traverse the plugin tree 2. collect allowed children / parents information from cms plugins 3. maintain a REST API endpoint 4. Add callback to the cmsplugin that gets the dynamic list of allowed children for current state of the database 5. and is used when the (+) menu is opened 4 and 5 are the ones that require changes to cmsplugin (djangocms) model itself -- 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/6c4daba9-a5ba-4d51-8969-4de4a6712e57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
