This is probably the wrong way as we should really take care of removing the permission we added, but I don't see a reason anyone would need to migrate back that far as auth wouldn't work anymore without XML api (and even so newer installs don't have the settings referenced so permissions are not automagically added by the migration). So noop is bad but acceptable to me.
Thanks @mmolitor87
This will prevent issues with service username formatting when access permissions are granted to the guest state. While users without mains cannot activate a service they could still retain an active account and it's possible to schedule a nickname update task which would subsequently error out.
Also it seems like a security issue if someone has a service account but their EVE character isn't known. cc8a7a18d23e9beb6e0a498a314e4c3bcae3f700 prevented accessing the services page without a main, now this ensures users don't have an account to manage.
Remove depreciated only_one decorator.
Prevent including task_self repr in key name.
Because some tasks are nested in a class, they use a task_self argument instead of the normal self which the celery_once package doesn't recognize to strip out.
Add nameconfig format for alliance_or_corp_ticker
Add nameconfig format for alliance_or_corp_name
Update docs for new nameformats
Correct missing dict key if no alliance.
Switch to dedicated add/remove endpoints.
Allow setting max cache age to None for infinite.
Apparently patch has issues.
Thanks @TargetZ3R0 and Discord devs <3
I have no idea why the order is reversing itself. Doesn't matter for functionality which of them comes first. This just checks they're both in there and a comma to separate them.
This will prevent those weird missing UserProfile and AuthGroup errors.
Add logging to authentication signals.
Correct reverse migration authservicesinfo creation.
Rename proxy models so they look better on the admin site.
The "empty" group will never appear as all users have a state so it has been removed.
I haven't yet found a good way to apply this to Teamspeak - perhaps go back to the token generation logic and create one with a user's state instead of "Member" and exempt those names from group sync?
Addresses #950
* Added in_organisation check to EveCharacter model
* Basic name formatter
* Switch mumble service to use name formatter
* Squash services migrations
* Add name to example service to allow it to be used in tests
* Add name formatter to services
* Add abstract views, model, form for services modules
* Refactor mumble service to new style
* Don't set credentials if setting a provided password
* Add success message to set password view
