Remove legacy single-remote storage in favor of remotes table #204
Reference in New Issue
Block a user
Delete Branch "fix/remote-storage-cleanup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Drops the legacy single-remote-storage feature (the per-profile
remote_storagecolumn plus all FTP/SFTP/S3/Google-Drive credential columns) in favor of the existing multi-remote#__mokosuitebackup_remotestable, which is created at install time.install.mysql.sql+02.52.25.sqlmigration).ftp/google_drive/s3fieldsets fromprofile.xml; drop the legacy UI intmpl/profile/edit.php(adds a "save first" prompt, usesgetOrCreateInstancefor the modal, readsitem.params).BackupEngine,SteppedBackupEngine, andloadRemoteDestinations()(the remotes table is guaranteed by install).remoteStorageproperty.try-without-catchintroduced mid-edit before commit).Notes
#__mokosuitebackup_remotesis created ininstall.mysql.sql, so fresh installs and migrated sites both have it.services/provider.phpdeletion, submodule bump, and module<name>rename were intentionally left out of this branch.Test plan