Trusted
1,351
edits
Changes
From Amahi Wiki
Upgrading ownCloud to New Version Releases (view source)
Revision as of 19:46, 15 November 2016
, 19:46, 15 November 2016→Upgrading ownCloud 8.2.1 to Nextcloud 10.x on Amahi
===Upgrading ownCloud 8.2.1 to Nextcloud 10.x on Amahi===
About June 1, 2016 one of the founders, some developers, and some staff broke away from the ownCloud organization. The result was the creation of a "fork" product based on ownCloud 9, called "Nextcloud". Nextcloud 9 was introduced as a "plug-in" replacement for ownCloud 9. However, due to severe bugs inherited from ownCloud the update/upgrade process did not function correctly. Later releases of Nextcloud 9.0.54 and 10.0.1 repaired the process. Unfortunately due to the broken process many Amahi users stayed with are still using earlier stable releases of ownCloud. Implementing Nextcloud would have resulted in users starting from scratch with new installations. This was is a big problem for instances that had have big collections of stored data and sharing configurations. Amahi has decided to go straight to Nextcloud 10.0.1. So the question, can we skip a major upgrade step (Nextcloud 9.0.54)? Well, kind of, with some issues, it is possible. This section will help you do with that.
The '''supported upgrade path''' should be for example; ''ownCloud 8.2.1 => Nextcloud 9.0.54 => Nextcloud 10.0.1''. This works flawlessly. The steps that follow are not '''not guaranteed''' to work for every new upgrade instance of Nextcloud 10. ownCloud 8.2.1 is the earliest release tested. If the upgrade steps do not work for a new upgrade instance you will have to start with a complete new installation. The Nextcloud Community will not help with issues where an upgrade step was skipped.
# Now do the usual upgrade process (i.e. via the browser GUI). The upgrade "should" complete successfully. '''DO NOT''' login to Nextcloud yet.
# Copy the original “index.php” and “version.php” files from the "known" location in to the “owncloud” directory, replacing the existing copies (this will overwrite the modified version.php).
# After the copying of the PHP files, restart the Apache server or rebootthe server.# Login to Nextcloud as the “administration user” and go to the “Admin” application. A scanning operation will begin in the “Security & setup warnings” section.
# After a period of time a warning message will appear in “red” stating that a “Code Integrity check...” failure has occurred.
# On the red line for this failure, "click" on the "Rescan" link. This will force a new Nextcloud scan. After the new scan the code check failure should disappear.
# Test the new instance. On the surface most things will upgrade correctly. ::*Sharing and data configurations tested worked "mostly". ::*Some applications may not upgrade correctly, usually disabling/enabling each application should fix the issue. ::*If using “External Storage Support”, there maybe a double entry for the same items. Delete the second one.
<br />
----
