Django-blog-lotus

--------------------------

A minor release with new feature *Sitemaps*, see
`Migration to 0.8.1 <https://django-blog-lotus.readthedocs.io/en/latest/migrations.html#from-0-8-0-to-0-8-1>`_
to know about migrating your project.

* Added a ``modified`` field on Category, Album and AlbumItem models. This was required
to have accurate update datetime in future ``sitemap.xml``;
* Added Sitemap classes for Article, Author, Category and Tag objects with test
coverage and documentation;

--------------------------

A major release with new feature *Article album*, see
`Migration to 0.8.0 <https://django-blog-lotus.readthedocs.io/en/latest/migrations.html#from-0-7-0-to-0-8-0>`_
to know about migrating your project.

**This will be the last major version to support Django 4.0, the next version will
require Django 4.1 at least.**

* Added new feature "Article album":

* Album holds items which can have a uploaded media;
* Article can select an Album to display in its detail view;
* This features comes with new models, factories, setting, template tag and tests;
* Updated ``lotus_demo`` command to create some albums to use in articles;
* API does not implement it yet and it will come in the next version;

* Improved quality task to include check-django;
* Adopted some django-ckeditor settings in sandbox for a better usecase with image
embedded in ckeditor contents;
* Added new meta tag in ``base.html`` to define canonical URL for every pages, this
needs to enable a new middleware in your Django settings to work. See migration
document for details;
* Pinned django-taggit to ``<5.0.0`` since the 5.x version drops support of Django 4.0
that we want to keep for Lotus 0.8.x version;
* Fixed task ``check-migration`` so it returns migration code instead of just signal
error when there is pending migration. This is required since Django 4.0 the Django
command ``makemigration`` has some behavior changes;
* Enabled CSS Grid from Bootstrap settings in sandbox frontend (since Grid is used to
display Album);
* Added API overview documentation;
* Added new stylesheet used in Lotus model admins to improve CKEditor width, this
configurable from settings;

--------------------------

A major release without almost no breaking changes, see
`Migration to 0.7.0 <https://django-blog-lotus.readthedocs.io/en/latest/migrations.html#from-0-6-1-to-0-7-0>`_
to know about migrating your project.

* Added API with Django REST framework (DRF):

* API is in beta stage for now, some improvements may come later;
* API is optional depending DRF is installed or not;
* API is read only, at least for now;
* Article, Author and Category have their own entrypoint;
* Listing and details use different serializers to avoid too large responses;
* Publication criteria and language filtering is properly implemented alike in HTML
frontend;

* Added new template tag ``article_get_related`` that is able to properly filter
related article queryset and use it in article detail template;
* Added new template tag ``get_categories`` to list all categories available in current
language;
* Added new template tag ``get_categories_html`` which do the same as
``get_categories`` but is rendered to HTML fragment from a template;
* Added filter on Category into Article admin list;
* Moved documentation to Furo theme;
* Restructured documentation and improved some parts;
* Fixed warnings about deprecated ``django.utils.timezone.utc`` in favor of
``datetime.timezone.utc``;
* Fixed warnings about Factoryboy deprecation with post generators and auto save using
``skip_postgeneration_save`` on every factory;

--------------------------

A minor version only to update ``.readthedocs.yml`` file to follow service deprecations
changes.

--------------------------

* **Added Django 4.2 support**;
* Removed path prefix ``articles/`` from detail view URL since it is useless;
* Added new setting ``LOTUS_CRUMBS_TITLES`` so crumb title for views can be customized
from settings. However this does not apply for detail views which directly use their
object title as the crumb title;
* Changed view so Lotus is compatible with single language project (when middleware
``LocaleMiddleware`` is disabled);
* Fixed admin views for Article and Category to not fail when there is an object saved
with language that are not available anymore;
* Added ``seo_title``, ``lead``, ``introduction``, ``content`` to searchable fields in
Article admin list;
* Added ``lead``, ``description`` to searchable fields in Category admin list;
* Added new filter to Article admin list to filter on published or unpublished items;
* Added logo and favicon to documentation and sandbox;
* Renamed some template blocks:

* ``head_title`` to ``header-title``;
* ``head_metas`` to ``metas``;
* ``head_styles`` to ``header-resource``;
* ``javascript`` to ``body-javascript``;

* Moved admin filters from ``lotus.admin.translated`` to ``lotus.admin_filters``;
* Upgraded to ``django-autocomplete-light>=3.9.7``;
* Removed temporary fix for DAL in Article admin change view template;
* Upgraded Sandbox frontend to ``bootstrap==5.2.3``;
* Added sidebar to Category detail to include some useful infos and links;
* Added publication state to part "Available in languages" in details;


Migrating from previous version
...............................

* Upgrade ``django-autocomplete-light``;
* Use the new template block names if you override some of lotus list, details
templates;
* If you mounted Lotus on root url path and standing on removed ``articles/`` path to
not pollute root path, you need to mount Lotus on path like ``blog/`` or even
``articles/``;
* If you used Lotus for a single language site, now you may be able to disable
``LocaleMiddleware``;
* Now you are able to edit Lotus crumb titles for index views, see settings
documentation for ``LOTUS_CRUMBS_TITLES``;

----------------------------

A fix release for migration missing callables for choices value and default
which leaded Django to require a new Lotus migration when changing language or status
settings.

Migrating from previous version
...............................

If you updated to the previous version and runned the wrong pending migration (which
should start with ``0002``) previously raised by Django, you need to remove it from
you migration history since the current version has fixed this invalid pending
migration.