Site bundles, metadata and the Twig tools of the platform #

This page is for developers who build or extend a Nexus site on Exponential Platform. These packages are the building blocks Nexus sites are made from. You normally do not install them by hand; the Nexus distribution requires them. Knowing what each does tells you where to look when a site behaves unexpectedly: a menu, a query type, a layout block or a legacy mapping is usually in one of them.

Repositories: se7enxweb/site-bundle, se7enxweb/site-legacy-bundle, se7enxweb/ngsymfonytools, se7enxweb/metadata-bundle, se7enxweb/mediata-ezpage-fieldtype-bundle, se7enxweb/ez-support-tools.

What each package gives a site #

The se7enxweb packages replace the upstream names through Composer replace declarations. site-bundle declares netgen/site-bundle:* as replaced (commit of 2026-04-19, release 3.0.6), so a project cannot end up with both the fork and the upstream copy installed side by side. See the upgrade notes.

Call Twig from a legacy template #

With ngsymfonytools active, a legacy .tpl can include a Twig template or render a Symfony controller.

1. Activate the extension (admin: Setup, Extensions; or in settings/override/site.ini.append.php):

   [ExtensionSettings]
   ActiveExtensions[]=ngsymfonytools

2. Regenerate the autoload array (admin: Setup, Extensions, "Regenerate autoload arrays"; or run the legacy script bin/php/ezpgenerateautoloads.php through exponential:legacy:script).

3. Include a Twig template:

   {symfony_include(
       'AppBundle:Test:test.html.twig',
       hash(
           'theAnswer', 42,
           'homepage', fetch( 'content', 'node', hash( 'node_id', 2 ) )
       )
   )}

Operators (from the extension's usage guide):

Changes in 2026: the operator no longer uses the templating service that Symfony 5 removed (2026-04-05); it asks the container for the twig service. On 2026-04-16 it briefly used the Twig\Environment::class id and went back to twig the same day, because the legacy bridge release v5.0.9 makes the twig service public (its TwigPass calls setPublic(true)), so legacy code can fetch it again. A class_alias at the top of the content converter keeps the old repository interface name working on Ibexa DXP 4.x and 5.0.

Limits #

• site-bundle and site-legacy-bundle are not standalone: they need a project built on the Nexus pattern.
• The metadata field type needs the platform kernel. On the legacy kernel use the xrowmetadata extension, which writes the same data.

Related pages #

• Extension pages: ngsymfonytools, ez-support-tools, xrowmetadata
• Platform features: Nexus starter, legacy bridge, platform administration interface, DXP skeleton, Layouts on the platform, PHP 8.5 framework forks, SQLite for Exponential Platform, AdminNeo database manager
• Specifications: platform package map, legacy bridge bundle, platform console command names, platform SQLite installer
• Upgrade notes: package forks and command renames
• Changelog: platform changelog
• History: site-bundle, site-legacy-bundle, ngsymfonytools, metadata-bundle, mediata-ezpage-fieldtype-bundle-main, ez-support-tools, ecosystem overview, ecosystem months, change ledger