Hi Angelo, Just checking back in to see what the latest thinking is on replacing the cmsplugin_filer_* plugins as far as deprecation timeline and possible paths for migrating to the newer djangocms-* plugins?
I haven't followed development on the new plugins closely so apologies if this has been answered/solved elsewhere. Thanks! John-Scott On Sunday, September 11, 2016 at 11:25:03 PM UTC-7, Angelo Dini wrote: > > Hello @john > > Yes we want to replace cmsplugin-filer with more specific plugins > following the Python Zen "Do one thing, and that good". For that matter we > are working on cleanup/improving some existing plugins to replace > cmsplugin-filer: > > - cmsplugin_filer_file > djangocms-file > - cmsplugin_filer_folder > djangocms-file > - cmsplugin_filer_image > djangocms-picture > - cmsplugin_filer_link > djangocms-link > - cmsplugin_filer_teaser > djangocms-teaser (though we do not update it > for now) > - cmsplugin_filer_video > djangocms-video > > This will mainly help us ship djangocms-installer and the default > installation on Aldryn with good and clean base plugins. Next step will be > to provide facilities to migrate older projects to these new plugins. After > that we will deprecate the old ones (will take some months though). We will > publish blog posts prior to this scenario :) > > -- 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/c1c299c1-d3ff-4e9b-8a98-c3fd4c3d0e37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
