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

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:

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

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:

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:

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 --

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,

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