Skip to content
This repository has been archived by the owner on Oct 13, 2020. It is now read-only.

django CMS 3 and Django 1.8+ compatibility would be nice #9

Open
bittner opened this issue Jan 9, 2016 · 4 comments
Open

django CMS 3 and Django 1.8+ compatibility would be nice #9

bittner opened this issue Jan 9, 2016 · 4 comments

Comments

@bittner
Copy link

bittner commented Jan 9, 2016

Maybe interesting from a UX perspective: django CMS 3.2 now offers content wizards. They are explained in a 30 minute YouTube video by Martin Koistinen on Google+.

Everything Is AWESOME

The details of the implementation are demoed starting at minute 11 in the video.

(The screenshot above is fake, sorry! It's just decoration.)

@ericamador
Copy link
Member

Sorry for the delay in responding to your issue. We are currently using both Django 1.8.10 and Django-CMS 3.2.0. Was there any particular problems you were running into when attempting to use the app with either Django 1.8.x or Django-CMS 3.x.x? I'll work on updating the documentation to make note that both of these are supported.

@ericamador
Copy link
Member

I'm going to close this since there has been no response, but feel free to re-open this issue if you have any further problems.

@bittner
Copy link
Author

bittner commented Jan 12, 2017

I think this was about front-end editing (to avoid having to go into the Admin).

Irritates me that this ticket is so unclear. Usually not my style, sorry! 😟

@ericamador
Copy link
Member

Ah, I understand now. I'll reopen this and investigate further when I can find the time. Thanks!

@ericamador ericamador reopened this Jan 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants