Hello John Thanks for your feedback. Our plan was to develop migration paths to these addons as we (Divio) won't actively maintain these addons anymore. If someone steps forward and does so, we could talk about commit rights. But as it is with open-source, we've no deadline on the migration path. We're currently heavily involved into various projects and had so far no client who wished to migrate.
I'm currently not aware of any changes that might break cmsplugin-filer but that can change of course, also with the introduction of Django 1.11 and/or other package updates. The new plugins are though production ready (and also used on live instances). The most consuming part of the migration is to write a management script to migrate the data and test it. On Sunday, 4 June 2017 07:11:28 UTC+2, John-Scott wrote: > > Hi Angelo, > > I may have misunderstood the roadmap for core addons > <https://www.django-cms.org/en/blog/2017/02/01/core-addons/>: > > Deprecated addons >> Some older plugins that you may have encountered are now deprecated and >> we advise against incorporating them into new projects. >> These are: >> >> - cmsplugin filer <https://github.com/divio/cmsplugin-filer> >> >> >> - Aldryn Style <https://github.com/aldryn/aldryn-style> >> >> >> - Aldryn Locations <https://github.com/aldryn/aldryn-locations> >> >> >> - Aldryn Snippet <https://github.com/aldryn/aldryn-snippet> >> >> We'll be developing migration paths to help users who have these >> installed in their projects move to newer, official core addons that >> provide the same functionality. > > > I thought that meant *Divio* made the decision to deprecate > cmsplugin-filer and would be developing migration paths. I haven't seen any > discussion on this list regarding this change, the blog is the only source > of details I've seen. It looks like cmsplugin-filer development stopped > last fall, but the README has not been updated to warn people away from > using it in new projects so it's not clear if it is 'officially' deprecated > or not. > > Are there any known upcoming changes in django-cms that will break > compatibility with cmsplugin-filer? Will pull requests/issues for > cmsplugin-filer be ignored going forward? Are the new favored plugins > production ready? A quick glance at the djangocms-picture README suggests > that beyond needing to do some sort of data migration, users would > potentially need to also update templates, settings, etc. Any other known > hurdles that will need to be addressed when paving the migration path? > > Happy to help test any proposed migration path of course! > > Thanks, > John-Scott > > > On Thursday, May 25, 2017 at 11:31:41 PM UTC-7, Angelo Dini wrote: >> >> Hello John, >> >> that is no Problem. It is still on our todo lists but we are a bit >> consumed from projects/client work. I can't really give an >> estimate/deadline as it's an open-source effort. I'm also very happy if >> someone could help or tackle the task. >> I'd announce it here or via Blog if I'll get to anything. >> >> Cheers >> Angelo >> >> On Thursday, 25 May 2017 21:29:29 UTC+2, John-Scott wrote: >>> >>> 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/b9a260ea-7a9f-42c8-adff-3ac9a1f83f06%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
