Skip to content
This repository has been archived by the owner on Dec 9, 2019. It is now read-only.

Consider implementing something like https://github.com/mazelife/django-redactor #16

Open
fission6 opened this issue Jan 7, 2013 · 2 comments

Comments

@fission6
Copy link

fission6 commented Jan 7, 2013

https://github.com/mazelife/django-redactor

for better / richer content editing in the admin for flatblocks.

https://github.com/mazelife/django-redactor

@martey
Copy link

martey commented Nov 1, 2013

I think there are a wide variety of different WYSIWYG editors, and that it does not make sense for django-flatblocks to require a specific editor. Redactor also has specific issues that make it unsuitable for inclusion under django-flatblocks' current license:

You just need to purchase the OEM license. No additional fees will be applied and there are no special terms or conditions, until Redactor is properly "linked" in your software.

However, keep in mind that Redactor is not an open-source product. It is proprietary commercial copyrighted software and we do not allow it's distribution under any open-source licenses. Think about Redactor as if it was a paid proprietary extension for your project.

It is also not clear that django-redactor has resolved these issues.

@zerok
Copy link
Owner

zerok commented Nov 1, 2013

Sorry for the day (for some reason I never saw a notification for this :-/). Since django-redactor is just basically an integration bundle offering form fields and widgets I don't really see what keeps you from integrating it yourself by re-registering the modeladmin instance, or am I missing something? :-)

And as @martey said, the license is definitely in and of itself a show-stopper for any further integration here.

tangochin pushed a commit to tangochin/django-flatblocks that referenced this issue Sep 15, 2016
Fixed some formatting in README.rst.
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

3 participants