- Permissions of 'gestion' app are correctly added to the staff groups
of associations.
- Add tests to ensure staff groups of COF and BDS are correctly setup.
- Shortcut functions are added to retrieve COF and BDS association.
- Fix some issues and improve efficiency of some RunPython code in
migrations.
- Merge some migrations.
- To simplify, any RunPython don't get a revert function.
Run 'bash provisioning/check_migrations_supportBDS.sh' from the vagrant
VM.
This will do the following:
- delete the existing database 'cof_gestion', if applicable,
- apply migrations to render the database as pre-supportBDS,
- the last pre-supportBDS migration of 'cof' app creates some instances
using old database schema,
- supportBDS migrations are applied,
- finally, the 'check_olddata' command of 'cof' app ensures data has
been correctly migrated.
This commit should be reverted before reaching production stage.
Move event-related models from 'cof' app to 'gestion' app.
Add 'Association' model to register name, related groups (buro,
members), etc.
Club is now associated with a single Association instance.
Migrations take care of these changes.
Profile view
- Let the user see his information.
- List the clubs whose he is a member.
Profile edition view
- Renamed from previous "profile" view
- User can now change "occupation" field.
Club detail view
- Informations about a club.
- Accessible by staff members and "respos" of the club.
- List members, with subscription fee (if applicable).
Club admin
- Change memberships of clubs added.
- 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
