yireo / magento2-additional-block-template
yireo/magento2-additional-block-template
N/A
Yireo AdditionalBlockTemplate
A Magento 2 module to allow for additional templates to be rendered, besides the original template.
Overview
When the Magento frontend renders its storefront, it uses the XML layout to position blocks all around. Each block can be rendered via a template and by default, this means that one block only has one template. Adding a new template right before the original template but with a new <block/> definition causes another $block object to be created. This module overcomes this shortcoming and simply allows you to add multiple templates to one single $block instance.
Installation
composer require yireo/magento2-additional-block-template
bin/magento module:enable Yireo_AdditionalBlockTemplate
Usage
Using the XML layout, you can reference a certain block and add your own template in front of the original template (before), after the original template (after) or right before the final closing tag in the original template (nest):
<?xml version="1.0"?>
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
<body>
<referenceBlock name="category.description">
<arguments>
<argument name="additional_templates" xsi:type="array">
<item name="example1" xsi:type="array">
<item name="template" xsi:type="string">Yireo_Example::example-before.phtml</item>
<item name="position" xsi:type="string">before</item>
</item>
<item name="example2" xsi:type="array">
<item name="template" xsi:type="string">Yireo_Example::example-after.phtml</item>
<item name="position" xsi:type="string">after</item>
</item>
<item name="example3" xsi:type="array">
<item name="template" xsi:type="string">Yireo_Example::example-nest.phtml</item>
<item name="position" xsi:type="string">nest</item>
</item>
</argument>
</arguments>
</referenceBlock>
</body>
</page>
Each item name (in this case example1, etc) can be retreived in the block template using $block->getAdditionalTemplateName().
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[Unreleased]
[0.0.4] - 22 October 2025
Fixed
- Add files
- Copy generic CI/CD files
- Pending changes
0.0.3 and earlier
- Initial releases
Requires 1
| Package | Constraint |
|---|---|
| magento/framework | ^101.0|^102.0|^103.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from yireo
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.