Recent changes
35934 changed pages · Atom feed · Recent comments · Recently added · Recent ratings
Wednesday November 04 2026
- Update stored component block identifiers (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Layouts from before the rename store components as ibexa_component_<type>; ext:explayouts:updatecomponentblockidentifiers renames them to exp_component_<type>. - Write down what the migration changed (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
List moved settings, imported layouts and their strategies, overrides added or removed - for the next migration. - Check the extension order after moving settings (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
After moving settings or adding extensions, check DesignExtensions[] and AvailableBlocks[] in effect. - Use exp:layouts instead of the old helper scripts (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The ext:explayouts:* helpers (block_list, layout_info, layout_copy, layout_list, rule_list, share_create, collection_list) run on their own again since explayouts 1.4.42; exp:layouts stays the tool for export and import. - Import beside the existing layouts (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
--strategy=copy imports items that already exist as new copies, leaving the originals. - Keep layouts in the project repository (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Commit exports next to the design extension; layouts.json in the archive can be compared between versions. - Freeze a Layouts site into templates (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
When a site must stop changing (an archive), its layouts can stay; freezing means fewer editors, not rewriting. - Move all layouts to another installation (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
exp:layouts export --all on the source, import with a dry run on the target; content is matched by remote ID and path. - Update stored block links to remote IDs (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
ext:explayouts:updatelinklocationreferences converts block links from ibexa-location://<id> to exp-remote-location://<remote id>. - Move the mappings with the layouts (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
--rules=none|selected|all decides which layout mappings travel; selected (the default) takes those of the chosen layouts. - Copy the menu settings to another siteaccess (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
exp:ini copy copies a setting (a whole array with its reset line) from one scope to another. - Merge layouts from two installations (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Import the second site's layouts with --strategy=copy where identifiers clash, then rename and remap. - Move a hard-coded menu into settings (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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 (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Many HTML snippet blocks with the same markup become one block type; replace them one by one. - Plan the way back (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Exports of the layouts, backups of the INI files (exp:ini keeps them in var/backup/ini/) and the previous extension release. - When the target lacks some content (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
--unmapped=drop|keep|fail decides what happens to references to content the target does not have (default drop). - Move content to another place in the tree (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
A move keeps node IDs: menus, Location mappings and manual collections follow; Path and Path prefix targets do not. - Move inline styles into the stylesheet (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
style="" and <style> in old templates go into your stylesheet, packed with the theme's. - Add a language and give it layouts (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
A new siteaccess gets its settings (menu.ini) by exp:ini copy and its own layouts by mappings with a Siteaccess condition. - Move only some layouts (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
--only with the layout identifiers; the shared layouts they link to come along.
