Is there an overview of django-cms for those not familiar with it? I looked around the project homepage and, surprisingly, I couldn't find anything that gives a high-level overview. For example:
* Is django-cms just a set of extensions to django that I could add individually and end up with django-cms, or it is more than the sum of its parts? * Related to this, is it possible/easy to take an existing django project and add the django-cms features without breaking anything? * What kind of projects would django-cms be the better solution for, and what kind of projects would it be best to stick with django? * Compared with django, is there any overhead involved in using django-cms? For example, if I develop a django application starting with django-cms but never use any of the cms features, will I pay a performance penalty? Thanks! (And it would be nice if this kind of information was available in an overview document on the django-cms project homepage.) Todd Wilson Jonas Obrist wrote, on 01/14/2011 09:31 AM: > The django CMS core team just released the third release candidate for > version 2.1. > > Download: http://pypi.python.org/pypi/django-cms/2.1.0.rc3 > Documentation: http://django-cms.rtfd.org > Source: https://github.com/divio/django-cms/tree/2.1.0.rc3 > > Please report any issues you find with this release to our issue tracker at > https://github.com/divio/django-cms/issues, thank you. > > Unfortunately, the release candidate 2 had a nasty bug in it which would > break our MPTT page tree when moderation is enabled and certain actions > were performed on certain types of trees. This issue was now resolved, > thanks to the amazing effort of Ųyvind Saltvik. > > There were also a couple of less serious bug fixes: > > * Issue 658, Invalid search fields on global page permission admin > * Issue 648, Frontend-editing on/off toggle fails when the current URL > contains an anchor. > * Issue 642, Short description of CMS plugins fails when no actual > plugin instance is available. > * Issue 641, 'PageUserForm' object has no attribute 'permission_acessor' > * Issue 639, get_page_from_request fails when not being called on an > admin URL but not a CMS admin URL. > * Countless documentation and testing improvements. > > Please help testing this third release candidate and enjoy our django CMS. > > In the name of the whole django CMS core developer team, > > Jonas Obrist > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
