-
☆ A M B ☆
- 24,524 Posts
If it isn't making the transport.zip package, then there's something wrong with it. Are you sure that you were logged in as the Administrator user when you ran Vapor?
Yes, I logged in as administrator.
Perhaps the Webhost doesn't have enough space or memory, but I think there's plenty of room.
-
☆ A M B ☆
- 24,524 Posts
Well, if it doesn't work for you then it doesn't work. You'll have to fall back to the basic "back up the site files, back up the site database, copy the site files to the new site, import the database to the new database, then fix your paths" method.
Usually running the Setup again in upgrade mode will fix most of the paths. Primarily, make sure the three config.core.php files (in the root, connectors and manager directories) have the correct paths, and the core/config/config.inc.php file has the correct database information (don't forget the $database_dsn line) and the correct paths. There are several places to check the paths, and especially the one for the assets_path, near the bottom, is easy to miss.
you might also try
https://github.com/Bruno17/migxBackupRestore
This is beta and based on
https://github.com/hvoort/MODxRevoBackup
You can create backup - setups in a MIGXdb - CMP, where you can define
folders, which you want to backup and if you want to backup the db, too.
Its possible to backup all at once in one zip or you can define part - backups.
When you restore at another installation, it does not overwrite the existing config-files and its possible to change configs before importing the db.
databackup is used internally by MODxRevoBackup and by migxBackupRestore
it does only the db-backup-part.
MODxRevoBackup and migxBackupRestore does all together
backup and restore of db and files.
with MODxRevoBackup you do the backup from outside of MODX and it does only a complete backup, but not of a core, which is outside the root.
with migxBackupRestore, you can define different backup-settings, which makes it possible to backup only parts of the files, if you have a large site, or if you want only backup parts, which change often.
You do the backup from Manager and it does backup also the core, if outside the root.
The restore part is done with the same (a bit extended) script from MODxRevoBackup.
Ok Bruno17, I'm a bit confused by
MODxRevoBackup is for backups,
migxBackupRestore is for restores.
It does only the db-backup-part (I'm assuming you mean MODxRevoBackup).
Your last line says MODxRevoBackup does the restore, but I thought migxBackupRestore would do the restore?
So, if I understand you correctly...
backup with MODX Manager and restore with MODxRevoBackup (not migxBackupRestore)?
I need the whole website backed up so I can FTP the file to my local computer where I have the local MODX server running to edit the website.
I can then push up to the live website if nothing's broken on the local MODX website.
databackup is only for db-backup
It is used by MODxRevoBackup and migxBackupRestore for the db-backup-part internally.
You can use either MODxRevoBackup or migxBackupRestore for doing the backup and the restore.
Its up to you, which one of them both you choose.
