Django-content-editor

Latest version: v7.1.0

Safety actively analyzes 687918 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 5

3.0

===================

- Added Django 3.0 and 3.1a1 to the test matrix.
- Dropped Django 1.11, 2.0 and 2.1.
- Fixed a problem where the content editor JavaScript code would produce
an invalid ``action`` upon submit.

2.0

===================

- Changed the minimum versions to Django 1.11 and Python 3.5. Removed
the dependency on six again.
- Dropped the ``contents_for_mptt_item`` utility.
- Dropped the ``PluginRenderer`` -- people should really either use
feincms3's ``TemplatePluginRenderer`` or implement a project-specific
solution.

1.5

===================

- Added an additional check to avoid processing inlines not managed by
the content editor.
- Allowed uncollapsing tabbed fieldsets after page load by specifying
``"classes": ["tabbed", "uncollapse"]``
- Added a place to edit items assigned to unknown regions.

1.4

===================

- Added configuration to make running prettier and ESLint easy.
- Added a different message when a region is empty and its ``inherited``
flag is set.
- Make the ``regions`` attribute on ``ContentEditorInline`` objects a
callable.
- Added a six dependency, Django 3.0 will ship without
``python_2_unicode_compatible``.
- Deprecated ``contents_for_mptt_item`` and removed the django-mptt
dependency from the testsuite.
- Made the dependency of our JS on ``django.jQuery`` explicit which is
necessary to avoid invalid orderings with Django 2.2 because of its
updated ``Media.merge`` algorithm.

1.3

===================

- Added back the possibility to move new content blocks in-between other
content blocks without having to save first. To achieve this the CSS
and JavaScript of the content editor was rewritten using `flex
ordering <https://developer.mozilla.org/en-US/docs/Web/CSS/order>`__
instead of modifying the order of elements in the DOM. This also
implies that reordering content blocks does not require deactivation
and activation steps anymore e.g. to preserve the functionality of a
rich text editor, possibly making it easier to implement custom
editors for individual plugins.
- Added a button to the content editor to toggle the content of inlines
(making reordering contents easier).
- Added a workaround for a bug with Django's responsive administration
panel CSS where form fields where shown below the 767px breakpoint
despite them being ``.hidden``.
- Reformatted the CSS and JavaScript code using `prettier
<https://prettier.io/>`__.

1.2

===================

- Fixed our use of internal API of ``forms.Media`` that will be removed
in Django 2.0.
- Fixed an elusive bug with our formsets handling. Newly added content
blocks have to be saved before they can be reordered.
- Fixed a handful of minor CSS bugs.
- Updated the documentation with a few improved recommendations.
- Moved plugin buttons before the dropdown.
- Removed the JavaScript's dependency on the exact ``related_name``
value of plugins.

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.