Skip to content

chore: Bump version to 2.1.1 #269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 29, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,14 @@
Changelog
=========

2.1.1 (2025-03-29)
==================

* feat: add `instance.get_classes` for template components by @fsbraun
in https://github.com/django-cms/djangocms-frontend/pull/268
* docs: Reference example template components


2.1.0 (2025-03-26)
==================

Expand Down
2 changes: 1 addition & 1 deletion djangocms_frontend/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,4 @@
13. Github actions will publish the new package to pypi
"""

__version__ = "2.1.0"
__version__ = "2.1.1"
1 change: 0 additions & 1 deletion djangocms_frontend/contrib/link/forms.py
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,6 @@ class Meta:

link = LinkFormField(
label=_("Link"),
initial={},
required=False,
)
target = forms.ChoiceField(
Expand Down
14 changes: 12 additions & 2 deletions docs/source/tutorial/template_components.rst
Original file line number Diff line number Diff line change
Expand Up @@ -262,11 +262,21 @@ Template components are a powerful tool for developers, but they have some limit
to configure the component. Advanced form configurations such as ``fieldsets`` are not available. If you need
to create a custom form for a component, you should create a custom component instead.
* **Limits of the template language**: The Django template language is powerful, but it has some limitations.
Classes are intantiated by default, for example. This is ok for ``widget=forms.Textarea``, but potentially not
Classes are instantiated by default, for example. This is ok for ``widget=forms.Textarea``, but potentially not
for more complex cases.

Examples
========

Trouble Shooting
The djangocms-frontend repository contains a small number of example components in the
`examples directory <https://github.com/django-cms/djangocms-frontend/tree/master/examples>`_.
They are taken from the `Bootstrap 5 examle page <https://getbootstrap.com/docs/5.3/examples/>`_
and modified to include the template component tags.

Examples are not installed through the package. You can copy them to your project and adapt them
to your needs.

Troubleshooting
================

If the component does not appear in the plugin picker, check the following:
Expand Down