- Nested inlines
- Limiting access to the events : you can only edit/create events linked to
associations you for which you have the `<assoc>.buro` permission.
BDS + COF
The permissions assignation is triggered by the `post_migrate` signal since the
permission table will only be populated after the migrations have been applied.
- Mark more strings for further translations
- in verbose names
- in the __str__ method
- Turn all verbose names into lowercase
- Add more verbose names
- Set an ordering on gestion.EventCommentField
- More database constraints on EventCommentValue
- `TextField` is not nullable
(https://docs.djangoproject.com/en/1.11/ref/models/fields/#null)
- `unique_together` constraint on the two fk
- The models are moved to the `gestion` app
- A new field `associations` is added
- The location and datetime fields are removed in favour of a new model
`EventTimeSlot`
- The old events are migrated to the new app and linked to the
`cof_buro` association
Upgrade to Django 1.11
- We upgrade our django packages to 1.11 (beta 1)
- We apply some necessary changes in the settings file
- We prepare to upgrade Django-autocomplete-light
- We upgrade some other packages
See merge request !179
Write modern-style urls
- Proper use of include
- Defining namespaces (I do not use them for now because many urls are
going to change)
- Do not try to reverse with old-style references: 'cof.views.XXX'
See merge request !178
Kerl/clubs support
- Add the club-related models
- Register them into the admin site in order to be able to play with them
See #133
See merge request !175
Change CofProfile to Profile in kfet/backends.py
- K-Fêt accounts are now linked to profiles
- There is no need to perform the `get_or_create` as long as the profile
creation has been automated.
- This file is now PEP8 compliant
See merge request !180
- K-Fêt accounts are now linked to profiles
- There is no need to perform the `get_or_create` as long as the profile
creation has been automated.
- This file is now PEP8 compliant
Specify `on_delete`
Two kind of files are affected:
- Models
- Migrations
You can use the `-Wall` flag to check that the warning `RemovedInDjango20Warning: on_delete…` is not raised:
python -Wall manage.py runserver 0.0.0.0:8000
See merge request !177
Django-autocomplete-light does not support the `modelform_factory`
anymore in recent versions. We are actually using an old version of dal
because of this.
This had to be dropped at some point… So now is a good time
- Proper use of include
- Defining namespaces (I do not use them for now because many urls are
going to change)
- Do not try to reverse with old-style references: 'cof.views.XXX'
- The autocompletion feature works again
- The template is a bit more readable (indentation)
- The `options` variable in the template is no longer a integer but a
boolean.
- Move the model
- Add some BDS-related fields
- Add an `associations` fields to be able to separate the clubs between
the different associations using groups
