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

Incompatibility with Django-CMS #42

Open
MarkusH opened this issue Feb 1, 2014 · 3 comments
Open

Incompatibility with Django-CMS #42

MarkusH opened this issue Feb 1, 2014 · 3 comments
Assignees
@apollo13
Labels
bug

Comments

@MarkusH
Copy link
Contributor

MarkusH commented Feb 1, 2014

See django-cms/django-cms#2560
@zerok
Copy link
Contributor

zerok commented Feb 28, 2014

Is this still relevant? The linked issue has been marked as resolved in upstream.

@MarkusH
Copy link
Contributor Author

MarkusH commented Feb 28, 2014

Yes, as the up2date Django-CMS changes the behavior of how cmsplugin columns are named. I don't know if there is a way to force Django-CMS to use the old naming convention. And I rather not change it in production but want to keep the problem to being fixed after EuroPython.

@02strich
Copy link
Contributor

I actually started looking into it, but upgrading to head involves more then working this issue, but also updating/adding some dependencies as things have been moved out of django-cms.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@apollo13 apollo13

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zerok @02strich @apollo13 @MarkusH