I have two XenForo licenses: one cloud and one self-host. My co-admin and I are in the process of migrating from cloud to self-host, and have been lazily auditioning prospective hosts for the last two months. This is the basic migration procedure I've been using:
1) Perform a clean installation of XenForo
2) Create a new db from the .SQL file in the cloud backup
4) Expand the cloud file backup over the top of the clean XenForo installation
5) In config.php:
7) In config.php: Remove the 'enableListeners' thing
This works fine with a clean install of 2.3.7 and a backup taken from our cloud instance when it was running 2.3.7, however it does not work with a clean 2.3.10 install + 2.3.10 cloud backup. With 2.3.10, after Step 5, XenForo reports that it's in the process of upgrading, and I'm unable to do anything else.
On a possibly related note: I noticed one subtle difference between our 2.3.7 cloud backups and the 2.3.10 ones: In the 2.3.7 backups, the SQL file included a 'create database' command that I always had to comment out in order for the import to work on our shared hosts. The 2.3.10 backups don't have this... which is kind of nice, but it tells me that something changed with how these cloud backups are generated, and that I might not be crazy for wondering if they're broken now.
Am I doing something silly, or might this be a bug?
1) Perform a clean installation of XenForo
2) Create a new db from the .SQL file in the cloud backup
4) Expand the cloud file backup over the top of the clean XenForo installation
5) In config.php:
- Add the line $config['enableListeners'] = false;
- Change the name of the db from the one used for installation to the one created from the cloud backup
7) In config.php: Remove the 'enableListeners' thing
This works fine with a clean install of 2.3.7 and a backup taken from our cloud instance when it was running 2.3.7, however it does not work with a clean 2.3.10 install + 2.3.10 cloud backup. With 2.3.10, after Step 5, XenForo reports that it's in the process of upgrading, and I'm unable to do anything else.
On a possibly related note: I noticed one subtle difference between our 2.3.7 cloud backups and the 2.3.10 ones: In the 2.3.7 backups, the SQL file included a 'create database' command that I always had to comment out in order for the import to work on our shared hosts. The 2.3.10 backups don't have this... which is kind of nice, but it tells me that something changed with how these cloud backups are generated, and that I might not be crazy for wondering if they're broken now.
Am I doing something silly, or might this be a bug?
