You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How it is at the moment
If updated from more than one major version behind the current version the user has to use the exact version of NC into the ncp-update-nc panel.
For example updating from NC version 23 should be done by manually loading NC v.24.0.8.
After that the user can use the "0" to get to the current version of NC25.
How it could be
If the user enters the "0" the newest version of the major version gets loaded. By using "0" again NC gets updated to the to the next major version even if this is not the most current major version.
This would make updating more simple for users.
Not sure if it is possible. Idea is from this forum question (German).
The text was updated successfully, but these errors were encountered:
It's possible, but not easy, because we would have to fetch all available nextcloud server versions. However, the update mechanism of NCP will probably change over the course of the next months anyways and then this will be easier to improve.
How it is at the moment
If updated from more than one major version behind the current version the user has to use the exact version of NC into the ncp-update-nc panel.
For example updating from NC version 23 should be done by manually loading NC v.24.0.8.
After that the user can use the "0" to get to the current version of NC25.
How it could be
If the user enters the "0" the newest version of the major version gets loaded. By using "0" again NC gets updated to the to the next major version even if this is not the most current major version.
This would make updating more simple for users.
Not sure if it is possible. Idea is from this forum question (German).
The text was updated successfully, but these errors were encountered: