yireo / yireo_themebyroute
yireo/yireo_themebyroute
Assign a specific theme to specific routes
Yireo_ThemeByRoute
Magento 2 module to allow a file app/etc/theme-by-route.json to determine which theme needs to be loaded for which route.
Installation
composer require yireo/magento2-theme-by-route
bin/magento module:enable Yireo_ThemeByRoute
Configuration
Create a file app/etc/theme-by-route.json similar to the following:
{
"Loki/luma": [
"cms/index/index"
]
}
Now, the Loki/luma theme is applied to all pages.
If you want to control under which circumstances which theme is applied, there is an advanced syntax as well:
[
{
"scope_type": "website",
"scope_code": "default",
"theme": "Loki/luma",
"pages": [
"cms/index/index"
]
}
]
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]
[1.1.2] - 01 December 2025
Fixed
- Add enabled config option
[1.1.1] - 22 October 2025
Fixed
- Allow psr/log 1 and 2 besides 3
[1.1.0] - 22 October 2025
Added
- Add advanced syntax
[1.0.3] - 30 September 2025
Fixed
- Fix matching of request URI
[1.0.2] - 30 September 2025
Fixed
- Also do a direct match on URLs
[1.0.1] - 10 September 2025
Fixed
- Change JSON filename to app/etc/theme-by-route.json
- Better README
[1.0.0] - 09 September 2025
Added
- Copy generic CI/CD files
- Adding all files to git via Yireo Command
- Initial release
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.1.2 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2025-12-01 15:53:18 |
| 1.1.1 | stable | Not tested | Not yet tested Details | 2025-10-22 11:15:59 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2025-10-22 08:48:03 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2025-09-30 09:29:32 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2025-09-30 06:56:38 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2025-09-10 14:21:46 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2025-09-09 08:00:40 |
Requires 5
| Package | Constraint |
|---|---|
| ext-pcre | * |
| magento/framework | ^103.0 |
| magento/module-store | ^101.1 |
| magento/module-theme | ^101.1 |
| psr/log | ^1.0 || ^2.0 || ^3.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.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Warning | 4 | 4 warnings (ruleset: Magento2) — 1 auto-fixable with phpcbf |
| PHPMD | Warning | 4 | 4 rule violations (UnusedFormalParameter:2, CyclomaticComplexity:1, NPathComplexity:1) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) |
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.