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

Reintroduce locale setting for fullcalendar views

See merge request !85

Reintroduce the locale settings that where falsely removed in !74 (afa4558a and 10667a08) -- while this setting is not needed in fc version 3 that the merge request referred to, stating them explicitly is needed in v5 that is used in our project currently.

set different color accents in admin interface when deployed for production

See merge request !82

Fc fix update

Closes #111

See merge request kif/akplanning!84

This resolves #111

Move background event color to scheduling init code instead of every single background event

Use name field instead of default string representation of AK in header field
Add some margin below to improve visual appearance

Update dependencies

See merge request !83

Use django debug toolbar

See merge request kif/akplanning!81

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

Add requirement
Adjust settings to load toolbar in debug mode
Add debug URLs

Improvements to fullcalendar loading

See merge request kif/akplanning!74

Nils Steinger authored 4 years ago and Benjamin Hättasch committed 4 years ago

This removes support for the explicit "locale: '{{ LANGUAGE_CODE }}'" setting,
but that should not be a problem as https://fullcalendar.io/docs/v3/locale
states:
> If you are simply loading one locale, you do not need to specify the locale
> option.

Use more pythonic way to calculate times and construct strings

Improve translation (and original strings)

See merge request !71

Add new Strings + Translations
Fix Typos
Remove event specific vocabulary