Actually, scratch that. We followed : https://github.com/owncloud/core/issues/23610#issuecomment-205704566 and were able to recover.
Crisis averted. No more willy-nilly upgrades! Thanks everyone. ~ Laz Peterson > On May 26, 2017, at 8:56 AM, Laz C. Peterson <l...@paravis.net> wrote: > > Hello everyone, > > I have a small problem. Before I start off, I want to disclose that I did > not read the upgrade instructions well enough — so please don’t be too harsh! > > Anyhow, so here’s the deal. I clicked the link on the upgrade documentation > that took me to the change log. From there, I clicked “ownCloud 9.0” and it > took me to version 9.0.9. I noticed that the version right below that on the > change log was version 8.2.11, which is what I was running. So I downloaded > this version, and upgraded the database; foolishly without backing up the > database. > > After the upgrade, I had all sorts of remote.php errors, and the files were > not showing up. Since I didn’t take a backup of the database, I was in a bit > of a pickle, and instead restored the old file structure for 8.2.11. > ownCloud decided to work with this, though the database had still been > modified for version 9.0.9. > > Ok ok, now please stop throwing tomatoes at me for not backing up the > database … > > What can I do to salvage the database situation? I guess what I’m asking is: > how can I find the SQL queries that run during each upgrade, to manually go > through and do the missing parts of the “upgrade process” to make it happy at > 9.0.9? > > Our intention is to go to the latest version … Any thoughts? > > ~ Laz Peterson > > _______________________________________________ > Devel mailing list > Devel@owncloud.org > http://mailman.owncloud.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@owncloud.org http://mailman.owncloud.org/mailman/listinfo/devel
