Skip to content
Open
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
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### More Changes - 2024-06-13

* added support for Django 4.2

### Changed

* removed RemovedInDjango40Warning warning message, thanks to @Ivan-Feofanov
Expand Down
1 change: 1 addition & 0 deletions CONTRIBUTORS.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,3 +9,4 @@
- [@tony](https://github.com/tony)
- [@tripliks](https://github.com/tripliks)
- [@Ivan-Feofanov](https://github.com/Ivan-Feofanov)
- [@ZTThomasOberthanner](https://github.com/ZTThomasOberthanner)
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,9 @@ django-inline-actions adds actions to each row of the ModelAdmin or InlineModelA

## Requirements

* Python 3.6.1 or newer
* Python 3.8 or newer
* Django 4.0, 4.1 or 4.2
* Django 5.0, 5.1 or 5.2 (experimental)

## Screenshot

Expand Down Expand Up @@ -230,7 +232,6 @@ If a staff user has clicked any inline action accidentally, they can safely clic
The current implementation for using intermediate forms involves some manual handling.
This will be simplified in the next major release!


In order to have an intermediate form, you must add some information about the triggered action.
`django-inline-actions` provides a handy templatetag `render_inline_action_fields`,
which adds these information as hidden fields to a form.
Expand Down
Loading