Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grappelli support #143

Merged
merged 2 commits into from
May 9, 2016
Merged

Grappelli support #143

merged 2 commits into from
May 9, 2016

Conversation

remik
Copy link
Collaborator

@remik remik commented May 6, 2016

Basic Grappelli support. There might be some glitches but overall it looks good.

This is small change for CSS and JS but double check would be nice. Thanks.

@coveralls
Copy link

coveralls commented May 6, 2016

Coverage Status

Coverage remained the same at 91.073% when pulling 68eee0d on remik:feature/grapelli into 3940883 on batiste:master.

@batiste
Copy link
Owner

batiste commented May 6, 2016

Cool I am happy you have time to work on the CMS.

I tested the PR but I couldn't see any changes? Is this merely about getting the compatibility going?

@remik
Copy link
Collaborator Author

remik commented May 6, 2016

You need to:

  • install pip install django-grappelli (make sure you have Django 1.9 or you will need install older version)
  • uncomment in settings.py and urls.py

@remik
Copy link
Collaborator Author

remik commented May 6, 2016

Also make sure I didn't break clean Django - I tested but you know double check is better.

@batiste
Copy link
Owner

batiste commented May 9, 2016

Sorry but I think my latest change created a conflict. Could you fix that and will merge just right after.

@batiste batiste merged commit 68eee0d into batiste:master May 9, 2016
@batiste
Copy link
Owner

batiste commented May 9, 2016

I merged with master. It seems to look fine for most of the things but the drag and drop dialog in the page list is unusable (css issue)

@remik
Copy link
Collaborator Author

remik commented May 9, 2016

Thanks. I will create issue (#144) for it and fix soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants