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

This way, the frontend views will be used when AKSubmission is installed and active, or otherwise the link to the built-in AK edit form in backend
This reduces the coupling between AKSubmission and other apps that previously needed that app
Use that new property in all places where previously an URL to the submission view was used (for consistency and to allow changes in one place in AKSubmission, too)
This implements #166

Make sure the custom add forms for event and room are correctly tested

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

Add bootstrap plugin (not included in fc by default anymore)
Activate compression
Make sure font awesome icons are used instead of loading bootstrap icons fc defaults to only for two buttons in fc
Remove copy-paste-error text in scheduler

Add compressor and sass compiler dependencies
Introduce corresponding settings
Use compressor in templates
Move only partially used dependencies to higher level for better re-usability
Add custom tags to create css and js for fontawesome separately
This implements the first part of #162

Upgrade Fullcalendar to v6 (implements #186)
Upgrade jQuery to v3.6 (implements #185)
Upgrade Select2 to v4.0.13
Remove tag information leftover in track manager

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)

Use official fontawesome django app for static file handling
Switch to fork/new version of django-bootstrap (for icon field and rendering shortcuts)
Add migration to bump icon field of dashboard buttons to new version
Update templates to load new app and use new tags

Bump django-bootstrap to version 5
Exchange bootstrap files (js & css)
Adapt settings
Migrate to new version/resolve breaking changes
Move layout adaptions previously included in bootstrap.css into custom.css

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

Add flag (default value true)
Use for wiki export
Add migration, translation & test
This implements #178

This remove the AKTags model and its usage in views, forms, templates, translations, and backup script
This implements #164

This implements #183

Make sure the more useful local times are displayed both in the form and on the list page

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 #174

This includes a new helper method to assert the existence of a particular message

Introduce framework to simply test correct rendering of views
Create tests for dashboard views
Create tests for plan views
Create tests for default admin views (add and change) of AKModel models

This implements #120

Make sure calendar is only loaded when event was already set

This implements #156

Load custom css in admin interface, too
Fix lading of locales in scheduler
Improve icon in scheduler
Reduce SQL query amount in scheduler

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

Adapt loading templates
Move plan loader template to AKModel
Add new template to load all css and scripts for availabilities with one call
Use that loader in views with availabilities editors

This used the common fullcalendar v5 instance instead of a special v3 version only for this editor
Improve visualization of availability deletion
Improve (event specific) timezone handling and remove dependency to moment-timezones

Create model
Create migration
Create admin interface

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

Use action with intermediate page instead of direct action for publishing and unpublishing of plans
This allows to create a link on the events detail page and on the status page to change the plans visibility
Add link to detail view
Visualize plan visibility on status page and allow to toggle it from there
This implements the final function of #159

Move loop-based action code to mixin that will only be used when more complex actions should be performed
Use queryset update function on existing actions to perform the necessary updating in only one db call instead of one query per entity
Additionally, visualize manually_resolved status in admin interface of CV