The update was a bit painful since I wasn't even sure how it goes with e107. I did it a few weeks back, and as far as I remember, I copied over first e107_v0.7.x_to_1.0.0_upgrade.zip, then e107_v1.x_to_2.1.4_upgrade.zip. Some useless messing around, then I discovered not being superadmin, fixed that and updated the db. Had a few localization and other minor errors, soon after I managed to rid the interface of those messages too.
I still have the backup folders of the above update steps in the VM, meaning I got the files of 0.7.23, 1.0 and the final 2.1.4. Unfortunately I only had the initial db backup saved, and seemingly I discarded that when I believed everything is up and running.
I had deleted and reinstalled the download plugin, if that's useful information. Didn't help much.
Since I can't see e107_files in the full package, how does that get generated? Is there a way to, for example, reset it? I don't even mind losing the downloads as long as the pages and news entries stay intact - if that's an option.
Or would, should something like that work, that I install a fresh e107 and replace it's db with the current's dump?