- Add a language and give it layouts A new siteaccess gets its settings (menu.ini) by exp:ini copy and its own layouts by mappings with a Siteaccess condition.
- Move content to another place in the tree A move keeps node IDs: menus, Location mappings and manual collections follow; Path and Path prefix targets do not.
- Site packages and layouts The site packages of this installation carry content but no layouts; install the layouts with exp:layouts import after the content.
- Check layouts after an upgrade After upgrading Exponential, export, list, open the main layouts in the editor and compare the pages.
- Check your template overrides after an upgrade Your copies of theme templates do not get the theme's fixes; compare them with the new theme versions.
- Check the extension order after moving settings After moving settings or adding extensions, check DesignExtensions[] and AvailableBlocks[] in effect.
- Different node IDs on staging and production Node IDs differ between installations; menus (MainMenuID) need the target's IDs, layouts are matched by remote ID and path.
- Rename layouts without breaking imports Imports match layouts by identifier; keep identifiers stable and change names freely.
- Split one installation into two sites Export the layouts of the site's subtree, import them on the new installation after its content.
- Merge layouts from two installations Import the second site's layouts with --strategy=copy where identifiers clash, then rename and remap.
- Rescue a layout broken by an import Import the previous export with overwrite and publish; the import purges the page cache itself.
- Move a hard-coded menu into settings An old template with links typed into it becomes a MainMenuID[] list read by the theme's main_menu.tpl.
- Replace copied HTML snippets by a block type Many HTML snippet blocks with the same markup become one block type; replace them one by one.
- Move inline styles into the stylesheet style="" and <style> in old templates go into your stylesheet, packed with the theme's.
- Write down what the migration changed List moved settings, imported layouts and their strategies, overrides added or removed - for the next migration.
- Velocity after a migration On a site served by Exponential Velocity, settings changes need exp:velocity restart, as exp:ini says.
- Rehearse the migration on a copy Run every command against a copy first; the dry runs on live then hold no surprises.
- Plan the way back Exports of the layouts, backups of the INI files (exp:ini keeps them in var/backup/ini/) and the previous extension release.
- The checklist after a migration Pages by markup, menus, mappings, drafts, caches, Velocity: the checks after moving.
- Template operators Every template operator registered on a development installation, grouped by family with parameters, input, return value and examples rendered on a development installation, plus how operators are registered, written…
Documentation license
This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.
Exponential Copyright © 1998-2026 Exponential Foundation and 7x