Disable requirements field completely instead of hiding it. This fixes AK editing which was broken when no requirements where configured.

This implements #199

This implements #212.

This ensures that it is always called when new AKs are created.
Additionally, editing of links in frontend is disabled, preventing diverging links between our tool and the wiki export.
This fixes #193 and #204.

Previously, indication was always open when no start and end dates were specified, now it is only active when an indication window was explicitly set.
Adjust the help text accordingly.
This resolves #198

Add docstrings
Remove code-duplications for dispatching user selection on submission overview
Remove code smells
Remove unused admin.py
Remove unused view in views

I think, that makes sense since it is supposed to be used by the graphical scheduling view

This is needed for correct document generation and besides like it should have been by convention anyhow

Redirect to submission overview when POST-only views are called via GET instead of crashing

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

Improve robustness of views against malformed/forged requests by checking whether the owner_id POST attribute is set before accessing it.
This fixes #187

Move AKModel views into several subfiles to improve overview and resolve problems with circular imports
Introduce new modular status page handling (widgets and views)
Port main status page to new structure
Move AK messages status page visualization to AKSubmission (therefore, they automatically do not show up when there is no possibility to create them)
Introduce status widget for virtual rooms
Fix timezone issue for rendering of AK messages on status page
Adapt status page URL in several views and tests

Benjamin Hättasch authored 1 year 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

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

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

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

Add a new link to edit form leading to owner creation form and passing the primary key of the edited AK/wish to that view
To realize that link, the corresponding field is excluded from the default form rendering and the rendering is triggered manually for that field (and the name field that should still appear on top)
When user is successfully created, they is set as owner of an AK, the user is redirect to the detail page of that AK and a message is displayed
Add corresponding test
This implements #96 and #86

Fix issue detected while creating test

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

This implements #120

This ensures correct loading if AKPlan is called from within a frame, e.g., in Venueless

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

Additionally, move moments library to common

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

This implements #144
Don't show slots, slot creation button, and availabilities for wishes on detail page
Don't create slots for wishes automatically (and don't ask for durations)
Automatically create one slot when wish changes to AK
Automatically remove all unscheduled slots when AK changes to wish

Implements #146
Show: AKs with comments, AK wishes with slots, AKs without availabilities, AKs without slots

This implements #129

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

This makes the usage of save(commit=False) obsolete that could cause issues for the creation of Availabilities (due to atomicy of transactions).