Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a way to handle module activation properly #1799

Closed
kelsos opened this issue Nov 25, 2020 · 0 comments · Fixed by #2421
Closed

Find a way to handle module activation properly #1799

kelsos opened this issue Nov 25, 2020 · 0 comments · Fixed by #2421
Assignees
Milestone

Comments

@kelsos
Copy link
Member

kelsos commented Nov 25, 2020

Problem Definition

When a user activates a module, the backend doesn't enable the module until the user logs in again.

The proper approach would be if the activation worked properly without the need for re-login.

Task

  • Add activation and deactivation code for all backend modules
  • When a module is activated or deactivated run that code.
@LefterisJP LefterisJP added this to the v1.10.0 milestone Nov 25, 2020
@LefterisJP LefterisJP modified the milestones: v1.10.0, v1.11.0 Dec 11, 2020
@LefterisJP LefterisJP modified the milestones: v1.11.0, v1.12.0 Dec 30, 2020
@LefterisJP LefterisJP modified the milestones: v1.12.0, v1.13.0 Jan 15, 2021
@LefterisJP LefterisJP modified the milestones: v1.13.0, v1.14.0 Jan 29, 2021
@LefterisJP LefterisJP modified the milestones: v1.14.0, v1.15.0 Feb 13, 2021
@LefterisJP LefterisJP self-assigned this Feb 22, 2021
LefterisJP added a commit to LefterisJP/rotkehlchen that referenced this issue Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants