If you are updating on a machine please follow these steps
*BEFORE* updating your code to this commit.

If you are installing on a fresh database and do not need to think
about existing data, ignore the following and proceed as usual.

1. Run the following migrations:
```
python manage.py migrate --fake scipost zero
python manage.py migrate --fake notifications zero
python manage.py migrate --fake partners zero
python manage.py migrate --fake affiliations zero
python manage.py migrate --fake commentaries zero
python manage.py migrate --fake comments zero
python manage.py migrate --fake finances zero
```

2. *** NOW UPDATE/PULL GIT ***
3. Run: `python manage.py migrate --fake-initial`

Due to the new Commentary request forms, which were
also used during vetting (choice=modify), the vetting
went wrong sometimes.
If the vetting action was 'modify', the user was redirected
to the old form which didn't exist anymore.

As a result of how the contruction of this modify structure, the Commentary
was first deleted and thus the data was lost. The requester did receive
a mail that his/her Commentary was accessible on SciPost however.

I fixed this by recontructing the vetting views. I combined the
vetting list and the vet request. I removed the action removing
the Commentary and made this a redirect to a new view which is
a modify page accessible only for EdCol Admins to modify+accept
the Commentary. Also, the mail for 'modify' vetting is also just sent
at *after* modification now.