Product guide
Redirect Map Manager
Validate a complete redirect plan, replace it atomically, keep its import history and export CSV, Nginx or Apache formats.
- Published version
- 1.2.6
- Compatibility
- WordPress 6.3 minimum ; 6.3, 6.9.7 et 7.1.3 testés, PHP 7.4 minimum ; 7.4.33, 8.3.36 et 8.4.27 testés sur le ZIP 1.2.5, CSV
- Product page (French)
- Gestionnaire de redirections
Prerequisites
| Component | Requirement |
|---|---|
| WordPress | 6.3 or newer |
| PHP | 7.4 or newer |
| Database | InnoDB for map and audit tables |
| Input | A reviewed CSV with source_url, target_url and decision columns |
WooCommerce is not required. The plugin interface uses English or its bundled French translation according to the WordPress locale.
Installation
Back up your WordPress database and installed plugin files. Keep the previous ZIP and test restoration before changing a live shop.
In the Novelience customer area, open Mes produits et licences (My products and licences). Download redirect-map-manager-1.2.6.zip (version 1.2.6) and compare its SHA-256 with the product page: fec0138c5082b3d5cf3632fa534f668284bcb98fb03b98ab463e9e109cc4ed86.
In WordPress, open Plugins › Add New › Upload Plugin, select the ZIP, and activate it. For an update, choose to replace the existing plugin in place; do not uninstall the old version first.
Check existing settings and run the product-specific checks below on your own theme, checkout and integrations.
Prepare the entire desired map. Each CSV row needs source_url, target_url and decision; reason is optional. Only redirect_301 decisions create active redirects.
In Tools › Redirect map, validate the file, review the plan and add an import note before confirming. Any invalid row, duplicate, loop, self-redirect or unauthorized target rejects the whole replacement.
Test representative paths and queries, and inspect the import history. Download and inspect CSV, Nginx and Apache exports before installing a server configuration.
Configuration
Prepare the complete CSV map and review host, path, query and fragment behavior. Every import replaces the whole active plan instead of merging rows.
Usage
On a disposable site, import a reviewed plan, request representative legacy URLs and check the target and import audit. Inspect exported CSV, Nginx and Apache rules before applying server configuration.
Update and rollback
Keep the old ZIP, a database backup and the complete previous CSV plan. Replace the plugin in place and verify the current map, history and representative redirects. To roll back a plan, import a complete reviewed prior plan; do not assume that removing the plugin restores old redirects. Avoid restoring an old database over new orders or content.
Limitations
- An import replaces the active map; it does not merge new rows into an existing plan. Removed rows are recorded in the history.
- Sources and targets must share the same complete host, with only the optional www spelling treated as equivalent. A different subdomain is not automatically allowed merely because the registrable domain is the same.
- Matching uses the request host and path. Query and fragment handling follows the validated target; a chain with an intermediate query or fragment is rejected.
- The map replacement is transactional only when all relevant tables use InnoDB. Validate exported server rules in your own server environment before applying them.
Published version
| Field | Current direct release |
|---|---|
| Version | 1.2.6 |
| ZIP | redirect-map-manager-1.2.6.zip |
| SHA-256 | fec0138c5082b3d5cf3632fa534f668284bcb98fb03b98ab463e9e109cc4ed86 |
The ZIP named above is the current Novelience direct release. A Woo Marketplace or WordPress.org package, if any, has its own review and publication state.
Support
Need help with installation or setup?
Written support is available in English and French.