Django-content-editor

Latest version: v7.2.0

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

Scan your dependencies

Page 3 of 6

4.0

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

- **BACKWARDS INCOMPATIBLE**: Plugins now use the inline prefix inside
the content editor. ``ContentEditor.addPluginButton()`` now requires
the inline prefix of plugins, not an arbitrary key. E.g. instead of
``<app_label>_<model_name>`` it now expects
``<app_label>_<model_name>_set``. This change allows using the same
plugin model several times with different inlines.
- Allowed configuring plugin buttons by setting the ``button`` attribute
of ``ContentEditorInline`` classes/objects.
- Added highlighting of the current content block in the editor.
- Added focussing of the first input field of new content blocks.
- Added a dragging affordance to content blocks.
- Made hovered and focussed content blocks stand out more.
- Fixed styling problems when using tabbed fieldsets with inlines.
- Fixed a long-standing bug where dropping a content block on top of
e.g. a CKEditor instance wouldn't actually move the dragged block to
the new position.
- Changed the JavaScript code to also handle Ctrl-S, not just Cmd-S to
save; modified the event handler to always save and continue.
- Replaced the collapse-all button with a checkbox to make it clearer
what the state is.
- Allowed collapsing individual content blocks by doubleclicking the
title. This may change in the future (as all things) because it's not
discoverable at all.
- Added a small note when a fieldset is collapsed.
- Changed CSS variables to use the same names as `django-variable-admin
<https://github.com/matthiask/django-variable-admin/>`__.
- Moved the ``Ctrl-S`` and ``Cmd-S`` shortcut handling into its own
``content_editor/save_shortcut.js`` static file to allow easier reuse
in other model admin classes.
- Started modernizing the JavaScript code, dropped Internet Explorer
polyfills. Django dropped support for legacy browsers in the
administration interface in the Django 3.1 release too.
- Changed the JavaScript code to not swallow unrelated drag/drop events.

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/>`__.

Page 3 of 6

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.