Security releases for django CMS 3.4, 3.5, 3.6 and 3.7

Hi folks. We have released security updates for django CMS versions 3.7.x, 3.6.x, 3.5.x and 3.4.x to address medium-level vulnerabilities. We recommend updating to version 3.7.4, 3.6.1, 3.5.4 or 3.4.7. The updated

Re: RELEASE: django CMS 3.6

On Wed, Jan 30, 2019, Daniele Procida wrote: >3.6 brings with it full support for Django 2.x, and drops support for >Python 2.7. Apologies - should be "drops support for Django 1.8, 1.9 and 1.10", not Python 2.7! Sorry if that caused any unnecessary alarm... Daniele -- Mes

RELEASE: django CMS 3.6

I'm very pleased to inform you that django CMS 3.6 is now officially available. 3.6 brings with it full support for Django 2.x, and drops support for Python 2.7. More details in the article above and in our changelog:

Re: Development to production

On Fri, Apr 13, 2018, crimsonfier...@gmail.com wrote: >Hello guys, > >I just want to ask some help if you can help me or show me a way to copy >everything from my development machine to a production one, specially >all things i did in django-cms because u cant see anything in the >documentation a

RELEASE: django CMS 3.4.6

Hello everyone, we've released version 3.4.6 (the latest release of the LTS version) of django CMS. The release contains bug-fixes, for a number of mostly minor issues. Release notes are available at <>. The new release is

RELEASE: django CMS 3.5.1

Hello everyone, we've released version 3.5.1 of django CMS. The release contains bug-fixes, for a number of mostly minor issues. Release notes are available at . The new release is available on PyPI. On Divio Cloud, the new version of the

RELEASE: django CMS 3.5

I'm delighted to inform you that we have made the official release of django CMS 3.5! Our weblog article above has most of what you need to know. The main thing to know is that this release of django CMS is significantly

django CMS 3.5 Release Candidate 1

Hi everyone. We've just issued the first release candidate version of django CMS 3.5. It's available from all the usual places: GitHub: Download: Documentation:

django CMS 3.4.5 released

Hi everyone - we're pleased to announce the release of django CMS 3.4.5, our first version with support for Django 1.11. . As ever, we value feedback, reports, patches. Huge thanks to everyone who contributed. Daniele

Re: Aldryn Newsblog and Django 1.10 (or 1.11 LTS) Support

On Thu, Aug 10, 2017, michael.sch...@rz.uni-augsburg.de wrote: >Is there a planned release date in the near future for django 1.11 support? Some time soon - we can't give an exact date, but we are working on it. Daniele -- Message URL: https://groups.google.com/d/msg/django-cms-developers/t

Now available: django CMS 3.4.4

I'm pleased to announce that version 3.4.4 is available. Many thanks to our core developer Paulo Alvarado who steered this release, and to all contributors. See the weblog for more details: Regards, Daniele -- Message

Re: djangocms-history And History

On Sat, Jun 17, 2017, Martin Owens wrote: >I've been following the djangocms-history project, and we have 0.4.0 >installed on the side to see what it can do. So far the history app, >doesn't seem to include any history. > >The functionality is undo and redo of changes pre-publish. There's no >

Security releases for django CMS 3.3 and 3.4

We've issued security releases (3.4.3 and 3.3.4) for two medium-level vulnerabilities. These updates prevent: * a potential escalation of privileges through a django CMS page's Advanced Settings. * a potential phishing attack using redirects from the login form The updated releases are now ava

django CMS 3.4.2 released

Hi folks, we're very pleased to have released version 3.4.2. In short, it contains: * the return of Revert to Live functionality * support for Django 1.10 * bug-fixes See for more information. Many thanks to everyone wh

Re: django CMS 3.4.2 release candidate 1

On Wed, Jan 11, 2017, Daniele Procida wrote: >>Hello all, the first release candidate of django CMS 3.4.2 is now >>available, containing some important new features and numerous bug fixes. > >Or, "will be available shortly" - I hadn't meant to press se

Re: django CMS 3.4.2 release candidate 1

On Wed, Jan 11, 2017, Daniele Procida wrote: >Hello all, the first release candidate of django CMS 3.4.2 is now >available, containing some important new features and numerous bug fixes. Or, "will be available shortly" - I hadn't meant to press send! Daniele --

django CMS 3.4.2 release candidate 1

Hello all, the first release candidate of django CMS 3.4.2 is now available, containing some important new features and numerous bug fixes. Highlights for this release are the return of the Revert to live functionality, and support for Django 1.10. More details:

Re: Feature idea: Page class attribute

On Thu, Nov 17, 2016, Brian Rutledge wrote: >In our templates, I'd like to be able to identify a page as being part of a >section of the site, so that we can apply section-specific CSS. My initial >thought on how to do this would be to add a class to the tag, but I >don't see an attribute on

Re: Creating page types programatically

On Tue, Sep 6, 2016, Patrick Heneghan wrote: >It might help for me to explain this in context - for example, I'm going to >have a "post type" called "blog", which should have title and content >fields, and then "event", which should have additional location, date, and >time fields. Hi Patrick

Re: unpleasant experience trying to bisect a change or regression

On Thu, Sep 1, 2016, Tim Graham wrote: >I'll >admit that I don't really understand how git merging works but I find >Django's cherry picking of commits to make backports to be very reliable in >terms of making history bisectable. Hi Tim. We're still trying to work out the right way to do th

Re: Inconsistancy of draft/public relations between pages (titles, and possibly extensions)

On Wed, Sep 7, 2016, Venelin Stoykov wrote: >There are cases when inconstancy can happen between Page.publisher_public >and Page.publisher_draft. One of the pages, for example public is pointing >to it's draft but the corresponding draft is not pointing the public >version. I already opened an

Re: Editorial workflow for django CMS (again!)

On Thu, Sep 8, 2016, Peter Bittner wrote: >I've started to compile a prototype of a django CMS powered website that >implements a simple editorial workflow. At the moment, I've use the board >weapons delivered with django CMS and vanilla Django (this is described a >little bit on Google+ [1]).

Re: What about to add a page copied signal?!

On Wed, Jul 27, 2016, Philippe O. Wagner wrote: >We are missing a signal that will be fired after a page was copied using >page.copy_page? >Would this be helpful for anybody else? What is the exact use-case? Is it: * a user-triggered copy action via the web interface * a copy invoked via the

Forward-porting from release/ into develop

In case you missed it, our branch policy is now that we work mainly on the latest release branch (bug-fixes, small improvements). However, we also do some work on develop (new features, backward-incompatible changes).

Updating documentation examples for Python 3

We received a pull request https://github.com/divio/django-cms/pull/5390, for a documentation example. The code sample uses a Python-2-style __unicode__() method; in Python 3 it would be __str__(). It’s quite right that this needs to be updated, but we’d like to do it in a more systematic way.

Activity report 10th June 2016

Dear django CMS developers, We want to keep everyone updated better about work that's going on in the project, so we are going to try posting weekly bulletins summarising work. These bulletins will cover django CMS itself, and also related projects in the ecosystem So, starting today, here’s