-
-
Notifications
You must be signed in to change notification settings - Fork 671
simplify logic of apps re-enabling #2140
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
Conversation
Signed-off-by: szaimen <[email protected]>
|
Aah, ok, so we'll let Nextcloud handle this, and only copy unsupported apps to the apps folder for easier re-anbling by the user? Are you sure we don't need to restore apps-status and all that? |
Yes, thats excactly what nextcloud/server#29020 has finally fixed ;) |
|
Tested and working! |
|
@szaimen Been having this in master now for a while and I have noticed that even core apps are missing/not enabled during update. We now got several reports regarding this, so I really think we should improve this. Something like:
That would guarantee that users easily can at least decide to enable the apps again through the GUI after a major upgrade were multiple apps are disabled. I don't trust Nextclouds app update/restore mechanism,.. :) |
|
I am not sure about this. Shouldn't Lines 1076 to 1096 in 0a3f0c6
|
|
You're right, sorry should have tested first. |
Close #2113
Disclaimer: I didn't test this.
Signed-off-by: szaimen [email protected]