If you set the CMSPLUGIN_ZINNIA_TEMPLATES, and every time you change it, django will make a new migration. Obviously this is not good since you don't want to accidentally make new migrations in 3rd party apps.
I believe the solution would be to manually set the choices arg on template_to_render inside the initial migration to the TEMPLATES setting found in models.py. That would make django dynamically check that variable rather than the hardcoded lists that are currently in the initial migration.
If you set the
CMSPLUGIN_ZINNIA_TEMPLATES, and every time you change it, django will make a new migration. Obviously this is not good since you don't want to accidentally make new migrations in 3rd party apps.I believe the solution would be to manually set the
choicesarg ontemplate_to_renderinside the initial migration to theTEMPLATESsetting found in models.py. That would make django dynamically check that variable rather than the hardcoded lists that are currently in the initial migration.