Django-content-editor

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

- Fixed the content editor initialization: The active region was only set after
saving and not initially.
- Removed the maximum height from content editor inlines.
- Started showing the target indicator again when dragging over collapsed
plugins.
- Allowed dragging plugins to positions *after* existing plugins, not just
*before*. This allows dragging a plugin directly to the end, finally.
- Changed the content editor to work better if changing the parent object isn't
allowed. Plugin buttons (which didn't do anything) are now hidden, and the
region tabs work correctly.
- Updated the bundled material icons font.
- Preferred the admin form's model instance to the ``original`` context
variable. This lets us pick better content editor defaults.
- Started hiding all plugin buttons when showing an unknown region.

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

- Stopped showing plugin buttons if user has no permission to add the plugin.
- Added Python 3.11, Django 4.1 and 4.2 to the CI matrix.
- Removed Django 4.0 from the CI (3.2 is still there).
- Added ``Type`` to ``content_editor.models.__all__`` since it is used in
feincms3.
- Tweak the plugin button positioning a bit.
- Added padding to form rows in tabbed fieldsets below 767px.
- Switched to hatchling and ruff.
- Started restoring not only the region but also the collapsed state of inlines
and the vertical scroll position.

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

.. _6.3: https://github.com/matthiask/django-content-editor/compare/6.2...6.3

- Increased the ``max-height`` of content editor fieldsets so that stupidly
high fieldsets stay completely visible.
- Changed missing icons to a generic extension icon instead of the question
mark.
- Added a system check for the ``regions`` attribute of content editor inlines.
It verifies that the attribute is either ``None`` or an iterable.

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

.. _6.2: https://github.com/matthiask/django-content-editor/compare/6.1...6.2

- Changed the handling of ``formset:added`` and ``formset:removed`` for
compatibility with Django 4.1.
- **POSSIBLY BACKWARDS INCOMPATIBLE:** Disallowed region keys which do not have
the form of an identifer, e.g. ``content-main``. Such keys cannot be used in
templates etc. and are therefore a bad idea.

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

.. _6.1: https://github.com/matthiask/django-content-editor/compare/6.0...6.1

- **POSSIBLY BACKWARDS INCOMPATIBLE:** Disallowed region keys starting with an
underscore. It was a bad idea to allow these in the first place and caused
some ... unnecessary interactions when wrapping ``Contents`` in lazy objects.
- Fixed an edge case where multiple machine messages were shown.
- Made it possible to move plugins out of unknown regions even if there is only
one valid region at all.

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

.. _6.0: https://github.com/matthiask/django-content-editor/compare/5.1...6.0

- Made the ``inherit_from`` argument to ``contents_for_item`` keyword-only.
- Added an optional ``regions`` argument to ``contents_for_items`` and
``contents_for_item`` which allows passing in a list of ``Region`` objects to
limit the regions fetched.
- Renamed the undocumented ``_regions`` attribute of the ``Contents`` object to
``regions``.