Move a site's settings into its extension #

The menu lists and theme settings live in the design extension's repository.

Life cycle: Migrate, example 8 of 34. Worked out on the Fit & Healthy site of Exponential 6.0.15+.

Contents #

1. In the Layouts editor
2. With settings
3. Which to choose
4. Check

In the Layouts editor #

Not in the Layouts editor.

With settings #

1. ./console exp:ini move menu.ini/SiteInfo siteaccess:site extension:mysite:siteaccess:site --dry-run shows the diff (on the test copy: would move 1 block, 7 variables, 1 file).
2. Without --dry-run it moves the block; the tool keeps the move only if the values in effect stay the same (it rolls back otherwise, unless --force). --only=MainMenuID,FooterMenuID limits it to some variables.
3. On the test copy, with mysite first in ActiveExtensions[], its siteaccess file was read after the theme's and the header menu list in effect was unchanged after the move.

Which to choose #

Version the settings with the templates that read them.

Check #

• exp:ini where menu.ini/SiteInfo/MainMenuID site shows the extension's file; the value in effect is unchanged.

Related pages #

• exp:ini for site builders
• Migrate examples, every page
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.