Database Update Scripts

[rclations]

There will be lots of database updates to run when upgrading to Largo 1.0

Some examples:

• Theme options will move to customizer settings
• Options framework will need to be parsed out and moved into customizer settings

[benlk]

Notes:

• the optionsframework option in wp_options is a serialized array of:
  • index 'id': the active theme options array's option_key
  • index 'knownoptions': all known Options Framework options arrays.

array (
  'id' => 'chicago_reporter',
  'knownoptions' => 
  array (
    0 => 'largo_dev',
    1 => 'chicago_reporter',
    2 => '',
  ),
)

• the theme options array is huge, and contains saved non-default options for everything in optionsframework_options(): https://github.com/INN/Largo/blob/master/options.php#L35

• the Customizer settings are stored in the option_key theme_mods_themeslug as yet another serialized array

[rclations]

@benlk this is great - could you go through and compile a list of everything we're saving in the database in the most recent version of largo?

Then you and I can go through the list, determine where things are moving to, and write db migration scripts for this.

[benlk]

By "everything" do you mean everything that's related to the theme, or also the custom meta things in posts and users and taxonomy terms?

[rclations]

everything that Largo stores in the database

[benlk]

Working on this here: https://gist.github.com/benlk/7ae3e024a91a57cd8d6c09f96234be5e