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

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

This resolves #143

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

This visualizes the state and allows to turn it on and off with a click

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

Make sure event is only loaded once
Massively reduce amount of SQL queries (e.g., plan view reduced from multiple queries per AK where over half of them are duplicates down to only 2 queries -- independent of AK count)
Replace software-side list constructions with in-database operations

adds datetimefield for start to Event model
adds datetimefield for start to Event model
adds translations
adds migration

This is done by generating the "now" timestamp from python instead of JavaScript using a newly created templatetag
The new "now" function is used in all AKPlan calendar views as well as in AKScheduling's scheduler view

Set content security policy for frame-ancestors to "*" for this view

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

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

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.

[refs #102]

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

Remove fullcalendar v4 from vendor directory (AKPlan)
Add fullcalendar v5 to vendor directory (AKPlan)
Adapt plan views to breaking changes (renamed properties and callbacks)
Fullcalendar 3 dependency for availability selection widgets stays untouched

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

Add boolean flag to events whether they should appear on the overview/start page or just when visiting the correct url

Add meta tags to display a preview for the linked page on twitter

Show full name of AK as tooltip
Scroll to current time

First part of #89
Also fix #87

Add field to model
Use field in form
Display field in ak detail view

Show track in ak detail view
Update translations

Add link to room detail view in slot table
Fix location based nesting in plan

Closes #60
Add boolean flag to event
Hide plan for non-staff users when flag is set
Update translations

Closes #77
Show link button for virtual rooms
Display capacity and properties
Link in detail view (plan and table)
Update translations

Remove typo from calendar JS

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

more general model

availabilities in AK submission
availabilities in AK wish submission

Closes #74