swissup / module-ignition
A beautiful error page and error tracking service for Magento
Ignition for Magento2
A beautiful error page and error tracking service for Magento
powered by spatie/ignition.
Installation
composer require swissup/module-ignition
bin/magento module:enable Swissup_Ignition
Using in developer mode
This module will show the error page with detailed information
about the error and stack trace only in developer mode:
bin/magento deploy:mode:set developer
Copying the error
The error page shows two buttons in the bottom-right corner:
- Copy stack trace – copies a PHP-style stack trace (exception class, message
and frames), ready to paste into a search engine or an AI assistant. - Copy message – copies just the exception message.
Pressing Cmd/Ctrl + C anywhere on the page copies
the full stack trace as well. If you have selected some text yourself, the normal
copy behaviour is used instead.
Reading the error from automation
When the page is driven by a browser-automation agent (Playwright, Puppeteer, …),
the same text is available without going through the clipboard.
A window.swissupIgnition object is exposed:
window.swissupIgnition.stackTrace; // full PHP-style stack trace (string)
window.swissupIgnition.message; // exception message (string)
window.swissupIgnition.report; // the underlying Ignition report (object)
window.swissupIgnition.copyStackTrace(); // returns a Promise, copies to clipboard
window.swissupIgnition.copyMessage();
The same strings are mirrored into hidden DOM nodes with stable ids, so they can be
read with a locator without evaluating JavaScript:
await page.locator('#swissup-ignition-stacktrace').textContent();
await page.locator('#swissup-ignition-message').textContent();
Using in production mode
You can also use it in production mode to log the errors using Flare
error tracking service. To do so, create flare project, get the "Project Key"
and run this command:
bin/magento config:set swissup_ignition/general/api_key [API_KEY]
bin/magento cache:clean
By default, only PHP errors are logged. If you would like to track JS
errors too, run this command:
bin/magento config:set swissup_ignition/general/enable_js_reporting 1
bin/magento cache:clean
Docker
When using Ignition with Docker the Open in Editor links will show incorrect paths.
To fix this issue open ~/.ignition.json file and add remote_sites_path and
local_sites_path settings.
Example:
{
"remote_sites_path": "/var/www/public",
"local_sites_path": "/Users/username/Sites/mysite/public"
}
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.3.2 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-08-05 12:56:05 |
| 1.3.1 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-06-23 13:01:38 |
| 1.3.0 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-06-16 14:07:28 |
| 1.2.1 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-05-28 08:33:37 |
| 1.2.0 | stable | Not tested | Not yet tested Details | 2026-04-29 15:02:49 |
| 1.1.6 | stable | Not tested | Not yet tested Details | 2025-02-26 13:09:23 |
| 1.1.5 | stable | Not tested | Not yet tested Details | 2024-11-20 15:05:33 |
| 1.1.4 | stable | Not tested | Not yet tested Details | 2024-09-02 11:09:42 |
| 1.1.3 | stable | Not tested | Not yet tested Details | 2024-07-15 06:17:42 |
| 1.1.2 | stable | Not tested | Not yet tested Details | 2024-06-10 14:53:24 |
| 1.1.1 | stable | Not tested | Not yet tested Details | 2024-05-08 14:59:19 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2024-05-08 11:49:43 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2024-04-23 09:09:01 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2024-04-04 15:35:47 |
Requires 2
| Package | Constraint |
|---|---|
| php | ^8.0 |
| spatie/ignition | ^1.13 |
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.
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 swissup
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.