XF 2.1 Test migration done, lots of settings tweaked - how to export/capture settings for next migration?

[Overscan]

So I've migrated my forum from SMF -> Xenforo 1.5, upgraded to 2.1, added some addons and customised a ton of settings, and the result is looking sweet as.

I'd like to redo the migration to test out some modifications to pm import handling, but obviously I can't just rerun the migration to my 2.1 forum- I'd going to have to start again from the beginning. Then, I'm going to do a real, final migration after that.

I can dump out the addons easily enough to a folder, and the modifications to extra.less, but what about all the colour settings, and other customised settings? It doesn't need to be importable, so long as it documents all the settings changes from defaults.

 

[Paul B]

The short answer is, other than the style, you can't preserve anything else,.

This thread explains the process: https://xenforo.com/community/threads/importing-guidelines.25325/

 

[Overscan]

Sadly, with the double migration from SMF - XF 1.5 - XF 2.1, it's not possible to use the strategy outlined in the post for repeating migrations. I'm going to try and find the settings in the database and script dumping them out.

 

[Overscan]

The SQL seems pretty readable - if I can figure out how to find all option_value that don't match default_value, I should be able to produce a list of all the changes I've made to the default settings. Sadly, my SQL skills are near zero. I might just dump the table to csv and do the compare in Powershell.

 

[DragonByte Tech]

SELECT * FROM xf_option WHERE option_value != default_value

EDIT: What you can do is this:

1. Duplicate the entire xf_option table into a new table, xf_option_backup
2. Export this new table as a SQL dump
3. After the final import, restore the xf_option_backup table
4. Run this:

   UPDATE `xf_option` AS option
       SET option_value = (
         SELECT option_value
         FROM `xf_option_backup` AS option2
         WHERE option2.option_id = option.option_id
      )

Entirely untested so you should test it before doing it live.

 

[Overscan]

Thanks, that's manageable even as a manual process.