pinax-teams
pinax-teams copied to clipboard
pinax
an app for Django sites that supports open, by invitation, and by application teams
mw_instance = middleware(handler) TypeError: object() takes no parameters File "/root/Desktop/pin/site/lib/python3.6/site-packages/django/core/handlers/wsgi.py", line 140, in __init__ self.load_middleware() File "/root/Desktop/pin/site/lib/python3.6/site-packages/django/core/handlers/base.py", line 39, in load_middleware mw_instance = middleware(handler) TypeError: object() takes no parameters
If a user has applied to a team I am unable to then add them to the team (in the case of the 'add someone' manager access) or invite them...
Hello, Looks a very nice package, where i can find the example documentation? Thanks
Currently no templates are included in the project.
As #33 notes, there is a backwards-incompatible change to _django-reversion_ that breaks semantic versioning. Rather than pinning to a particular version or updating _pinax_teams_ to be compatible, I'm wondering if...
Adds the ability to nest Teams. Remaining: - [ ] Standardize convenience methods for `ancestors` and `descendants`. - [ ] Document new templates and add to the appropriate starter project....
Also write tests that exercise `WSGITeamMiddleware` (which may involve customizing the test runner).
- Document signals (similar to [`django-user-accounts`](http://django-user-accounts.readthedocs.org/en/latest/signals.html) - Demonstrate usage pattern with `eventlog` (similar to what is set up in [`pinax-project-account`](https://github.com/pinax/pinax-project-account/blob/master/project_name/receivers.py)
- `team_manage` should implement a check similar to `team_update` - the following views compare `manager_access` to a `Team.MEMBER_ACCESS` constant, rather than checking the `member_access` attr: - `team_apply` - `team_accept` -...
