etechflow / module-redirect-manager
etechflow/module-redirect-manager
301/302 redirect manager with auto-redirect on URL-key change and a 404 catcher.
Etechflow_RedirectManager
A 301/302 redirect manager with a built-in 404 catcher for Magento 2 / Adobe Commerce.
Part of the Etechflow SEO Suite. A leaner alternative to the redirect tools in Mirasvit/Amasty.
Features
- 301 / 302 redirects managed from the admin (grid + add/edit form), per store view, with an
active toggle, internal notes, and a live hit counter per redirect. - Runs before
urlrewrite— a custom router (sortOrder 15) so managed redirects take
precedence over catalog/CMS URL rewrites. - 404 catcher — every not-found URL is logged (with hit count + referrer). One click on a
404 row creates a draft redirect and opens it for you to set the target. - Target can be a path (
new-page) or a full URL (https://…). - Fully flag-gated — master switch (off by default); inert until enabled.
- Configurable exclude regex so static assets / noise aren't logged.
Where it lives
- Marketing → Redirect Manager → Redirects — the redirect grid
- Marketing → Redirect Manager → 404 Log — captured 404s + "Create Redirect"
- Stores → Configuration → Etechflow → Redirect Manager — settings
Configuration
| Path | Default | Notes |
|---|---|---|
etechflow_redirectmanager/general/enabled |
0 |
Master switch (engine + 404 logger) |
etechflow_redirectmanager/redirects/default_type |
301 |
Default status for new redirects |
etechflow_redirectmanager/log404/enabled |
1 |
Log not-found URLs |
etechflow_redirectmanager/log404/exclude_patterns |
asset regex | Paths matching are not logged |
URL-key changes
Magento's native "Create Permanent Redirect for old URLs" (Stores → Configuration → Catalog →
Catalog → Search Engine Optimization) still creates url_rewrite 301s on product/category URL-key
changes. This module's 404 catcher backstops anything that slips through, so you can convert it
to a managed redirect in one click.
Install
bin/magento module:enable Etechflow_RedirectManager
bin/magento setup:upgrade
bin/magento setup:static-content:deploy <locale> -f --area frontend # prod: setup:upgrade clears var/view_preprocessed
rm -rf generated/code/* generated/metadata/* # di:compile won't clean this itself
bin/magento setup:di:compile
bin/magento cache:flush
bin/magento config:set etechflow_redirectmanager/general/enabled 1
Tables
etechflow_redirect— managed redirects (request_path → target_path, type, store, active, hits)etechflow_redirect_404_log— captured 404s (request_path unique per store, hit upsert)
Tests
vendor/bin/phpunit -c dev/tests/unit/phpunit.xml.dist app/code/Etechflow/RedirectManager/Test/Unit
Changelog
All notable changes to this module are documented here.
v1.0.0 — 2026-06-05
Initial public release.
301/302 redirect manager + 404 catcher. Admin grid + hit counters, custom router runs before urlrewrite. One-click create-redirect from a 404 row.
Requires 5
| Package | Constraint |
|---|---|
| magento/framework | >=103.0 |
| magento/module-backend | >=102.0 |
| magento/module-cms | >=104.0 |
| magento/module-store | >=101.0 |
| php | ~8.1.0||~8.2.0||~8.3.0||~8.4.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 | Fail | 16 | 1 error, 15 warnings (ruleset: Magento2) — 1 auto-fixable with phpcbf |
| PHPMD | Warning | 3 | 3 rule violations (MissingImport:1, ErrorControlOperator:1, UnusedFormalParameter:1) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 5 | valid; 5 advisory notes (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
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 etechflow
View vendorDynamic 'View Other Options/Finishes/Sizes' PDP buttons driven by per-product link attributes; replaces hardcoded in-description buttons and strips the old ones at render time.
Theme-agnostic mega menu for Magento 2. Renders on Hyvä, Luma, Adobe Commerce default and custom themes via automatic runtime detection. Provides a JSON endpoint for lazy-loaded subcategory + featured-product data.
EtechFlow Store Locator — admin-managed store/branch finder for Magento 2 with a Leaflet + OpenStreetMap map and postcode proximity search (postcodes.io). Hyva and Luma compatible. No paid map API key required.
Universal Product Fitment Finder for Magento 2 — Make/Model/Year/Part filtering on any fitment domain (automotive, motorcycle, marine, RV, phone cases, watches, appliance parts, anywhere a customer asks "will this fit my X?"). Admin-configurable labels + URL prefix so the same module rebrands to any merchant domain. Includes PDP fitment badge, SEO URLs, customer garage with cross-device sync, OEM/part-number search, and admin tooltips throughout. Theme-agnostic — Hyvä, Luma, custom themes. Renamed from "module-vehicle-compat" in v2.0.0.
Turn 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.