Fundementally the updater.php system does work well but only if trivial user config settings change from version to version of ICEcoder. If however, there's significant changes such as moving where config, plugin, backup data is kept and the contents of those files, it doesn't work. There's also the fact that when updating, it uses the updater.php from the current version and not new version, so migrating any kind of changes is impossible to predict.
So the updater.php system is made dormant for now, until a better plan can be implemented.
Ideas may include:
Download the new version, unzip it and use that updater.php, not the updater.php of the current version
Determine if there's a workable migration path and what that is. eg, if the user is on 8.1 and wants to upgrade to 8.3, they should be taken through migration steps 8.1 -> 8.2 -> 8.3. If any part of that journey is deemed to have changes that would block a migration, don't offer an automated update.
It's worth noting that the update shows a CSRF fail screen but has installed a fresh version of ICEcoder, as it fails to copy over any config files from old version to new so you simply get a new version.
Fundementally the updater.php system does work well but only if trivial user config settings change from version to version of ICEcoder. If however, there's significant changes such as moving where config, plugin, backup data is kept and the contents of those files, it doesn't work. There's also the fact that when updating, it uses the updater.php from the current version and not new version, so migrating any kind of changes is impossible to predict.
So the updater.php system is made dormant for now, until a better plan can be implemented.
Ideas may include: