I'll be porting the fix to the other core addons, will try to release them around early next week.
On Wednesday, 16 November 2016 20:20:12 UTC+1, Brian Rutledge wrote: > > I posted this issue to djangocms-style > <https://github.com/divio/djangocms-style/issues/32>, but it seems to me > that it affects multiple plugins, so I'm re-posting the description here. > > I just upgraded to 2.0.0, and discovered that setting > DJANGOCMS_STYLE_CHOICES and DJANGOCMS_STYLE_TEMPLATES results in changing > the choices for class_name > <https://github.com/divio/djangocms-style/blob/master/djangocms_style/models.py#L85-L90> > > and template > <https://github.com/divio/djangocms-style/blob/master/djangocms_style/models.py#L67-L71>, > > which necessitates new migrations. It looks any djangocms plugin that uses > this pattern (-link, -picture, etc.) will display this behavior. I am not > an expert on migrations, so it's not clear to me what problems it might > cause, but it make me nervous about future conflicts, and having migrations > outside of source control. > -- 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/b2c1cd1b-407a-457e-b8b2-8bd5f74f93fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
