Hello Brian The high-level goals for us was to create a simple undo/redo functionality for the current session of a user, as this is the most reliably and used way of history management.
If you'd like the previous versioning management back (revision) I'd highly encourage you to checkout and contribute to: https://github.com/Blueshoe/djangocms-reversion2 Cheers, Angelo On Friday, 30 June 2017 14:33:18 UTC+2, Brian Rutledge wrote: > > Thanks, Angelo. Do you have any kind of roadmap or high-level goals for > djangocms-history? For example: is reverting to a previously published > version of a page something that you have considered, and have ideas about > how it would be implemented? > > On Thursday, June 29, 2017 at 2:48:34 AM UTC-4, Angelo Dini wrote: >> >> Hello Brian >> >> we did not stop development, just re-focused now on django CMS 3.5.0. >> >> if a Client requests further improvements we will add them to this >> repository. This does not mean the community can contribute as well :) >> >> Cheers, >> Angelo >> > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to django-cms-developers+unsubscr...@googlegroups.com --- 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 django-cms-developers+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/efdb0b3c-858a-4a6f-b540-908655d0714c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
