Introduce model (including migration and admin interface)
Integrate into new event wizard
Display as property in details representation (e.g., used in scheduler)
Allow to choose types in AK add/edit forms
Show type info on AK detail page and in overview table
Adjust tests (including new tests for requirement and type visibility in submission form)
Update translations

Benjamin Hättasch authored 11 months ago and Nadja Geisler committed 11 months ago

Use plain html functionality instead of bootsrap datepicker.
Remove datepicker dependency.
This resolves #200 (datepicker not loading since load from CDN is blocked by CSP).
Improve how form media is loaded in event wizard.
Additionally, improve which fields are shown (and how) in event wizard.

Add or complete docstrings
Remove code smells
Disable irrelevant warnings
Update translations to changed line numbers and line breaks
Move duplicated code for event field pre-population and event timezone adaption to mixins

This implements #175

Use One2One relationship instead of inheritance
This allows to add and also remove the virtual features of a room

Introduce new model
Create migrations to migrate from existing to new model + a squashed version knowing only about the new model for fresh installations
Adapt admin views
Add django-betterforms as dependency to simply create a form allowing to generate rooms with optionally a virtual component in a single view and create that form
Add view to create rooms in that view and use instead of default django creation form
Use the new name/structure in templates
Move RoomForm to forms.py to make imports easier
Update batch creation of rooms

This resolves #150 and also resolves #179 since now rooms and virtual rooms (rooms with virtual features) are created using the same view

Upgrade django to 4.1
Upgrade django-timezone-field, django-simple-history, django-debug-toolbar and django-bootstrap-datepicker-plus
Upgrade mysqlclient
Remove obsolete pytz
Adapt timezone handling code to new interface of TimezoneInfo (part of python since 3.9 and backport included in 3.8)
Drop support for python 3.7 (since Django 4 requires >= 3.8)

This implements #183

Add start and end inputs below the calendar widget that can be used to add new entries to the calendar.
Inputs are based on html5 widgets, will fallback to simple text inputs in very old browsers. Modern browsers also provide an integrated validation of the time ranges. In older browsers, this will be done latest on server side.
This implements #124

This implements #156

Create new view (including template and form)
Link on status page
Add translations

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Add three admin actions to mark CVs as resolved, or set the level to 'warning' or 'violation' -- each including a preview/confirmation step
Introduce a generic view inheriting from the generic admin intermediate view to handle confirmations for admin actions (performing on multiple, freely selected items)
This implements #154

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This allows specifying the parameters without the need to know the GET keys
Also resolve double-compiling issue and thus switch from custom version of django-tex to the latest official release
Minor improvements to generic admin action view
This implements #152

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This mostly implements #159
Introduce a new field that denotes the timestamp when the plan was published
Introduce admin actions to publish and unpublish the plan and set that timestamp accordingly
Prevent other means to change visibility of the plan
Use that timestamp to only highlight recent changes when they occurred after the plan was already published

Introduce a new generic view that can be used for all admin actions that require a preview/confirmation or a form to specify parameters
Change AK Orga Message deletion view to use this generic view instead of a manually adapted delete view

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Make sure plan is hidden by default and allow to adapt/change this during the usage of the wizard
This fixes #115

The wizard is used instead of the normal built-in creation workflow
It consists of multiple steps to specify the most fundamental settings (especially the timezone), further settings, copying AKCategories and AKRequirements from existing events and activating the event once the basic configuration is done
The steps after the creation (first two steps) can be skipped