Product guide
Domain Context Router
Resolve a developer-defined context for one WordPress installation served through multiple allowed domains.
- Version publiée
- 1.2.1
- Compatibilités
- 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.0, Une installation WordPress ; WooCommerce non requis, Configuration PHP, DNS et HTTPS de chaque domaine à prévoir
- Fiche produit
- Novelience Contextes de domaines pour WordPress
Prerequisites
| Component | Requirement |
|---|---|
| WordPress | 6.3 or newer |
| PHP | 7.4 or newer |
| Configuration | Developer-owned filters for allowed hosts and context resolution |
The extension is code-configured. It does not provision DNS, TLS, a proxy or a CDN and does not require WooCommerce. It has no administrative settings screen or plugin data table.
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 domain-context-router-1.2.1.zip (version 1.2.1) and compare its SHA-256 with the product page: cd5b5e6a5672ba188fb89d6770f0583c115e01d64697d24a2913d954119cc7bc.
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.
Provide the allowed entry hosts through wp_domain_context_allowed_hosts and map them to contexts through wp_domain_context_resolve in your own project code.
If local application assets use other known origins, add only those origins through wp_domain_context_application_hosts. Do not add a third-party CDN if its URLs must stay unchanged.
Test each allowed and refused raw Host value. Inspect the context function, body class, response header, home/site URLs and archive canonical URLs.
Configuration
Declare allowed entry hosts with wp_domain_context_allowed_hosts and resolve contexts with wp_domain_context_resolve. List only application asset origins that may be rewritten.
Usage
Request each allowed domain and an invalid raw Host. Check wp_domain_context(), the body class, X-Site-Context and canonical URLs while confirming third-party URLs remain unchanged.
Update and rollback
Replace the ZIP in place and recheck configured hosts, third-party resources and canonical behavior. Keep your project-code configuration and the old ZIP for rollback. Because this plugin creates no own data table, it has no plugin-data uninstaller; removing it does not remove your custom filters or DNS configuration.
Limitations
- The raw Host is validated before normalization; invalid credentials, paths, queries, fragments, backslashes and ports are refused.
- Only explicitly allowed application origins are rewritten. Third-party resources are left unchanged.
- This is one WordPress installation and one database, not Multisite, tenant isolation or a security boundary between domains.
- The theme, server, cache/CDN and SEO plugin can affect canonical behavior. Test the complete deployment rather than relying on activation alone.
Published version
| Field | Current direct release |
|---|---|
| Version | 1.2.1 |
| ZIP | domain-context-router-1.2.1.zip |
| SHA-256 | cd5b5e6a5672ba188fb89d6770f0583c115e01d64697d24a2913d954119cc7bc |
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
Une question sur l’installation ou la configuration ?
Le support écrit est proposé en français et en anglais.