# ho-nl/magento2-reachdigital_storeresolver

`composer require ho-nl/magento2-reachdigital_storeresolver`

Canonical URL: https://packagento.com/ho-nl/magento2-reachdigital_storeresolver

## At a glance

- **Vendor**: ho-nl (https://packagento.com/ho-nl.md)
- **Latest version**: 1.0.8 — released 2025-01-31
- **Pricing**: Free
- **Package type**: Magento 2 module
- **Status**: active, accepting new buyers

## Installation

Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them.

1. **Sign in or create an account** at https://packagento.com/customer/account/.

2. **Add the package to your account.** Open https://packagento.com/ho-nl/magento2-reachdigital_storeresolver and complete the free checkout. A licence is minted automatically.

3. **Create or pick a project, then activate the licence on it.**
   - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/.
   - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project.

4. **Add the project credentials to your Magento codebase.**

   Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`:

   ```json
   {
     "http-basic": {
       "packagento.com": {
         "username": "ppk_live_...",
         "password": "psk_live_..."
       }
     }
   }
   ```

   Add the Packagento Composer repository to `composer.json`:

   ```json
   {
     "repositories": [
       { "type": "composer", "url": "https://packagento.com" }
     ]
   }
   ```

5. **Install and apply.**

   ```bash
   composer require ho-nl/magento2-reachdigital_storeresolver:*
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```

## README

[Changelog](CHANGELOG.md)

You are running a multi store with a specific catalog per domain.

### Installation
```BASH
composer require reach-digital/magento2-storeresolver
```

### Automatic mapping from Domain > Store View
With the new implementation for the `StoreResolverInterface` the domains automatically get mapped to the correct store view. This reduces the need to modify code to get new domain names working.

1. Register your domain
2. Point the A-records to your server 
3. ~~Change index.php, .htaccess or nginx_config file to activate your domain name~~ `StoreResolver` solves this for you.

### Add Store Code to Base URL
Store code will be removed from URL if added in the Base URL.
Make sure to explicitly set `Base URL for Static View Files` and `Base URL for User Media Files` without the store code

| Configuration                   | Value                           |
| ------------------------------- | ------------------------------- |
| Base URL                        | https://www.website.com/de/     |
| Base URL for Static View Files  | https://www.website.com/static/ |
| Base URL for User Media Files   | https://www.website.com/media/  |

> It's not possible to have CMS pages with the same identifier as a store code!

> Important note:  
Base URLs which have no custom string set after the TLD, must be configured at website level, not on store level,
else matching on URL can result in multiple stores, see `\Ho\StoreResolver\Model\StoreResolver::getAutoResolvedStore`

### Store scope definition

| Product                      | Default | Website | Store Group | Store View |
| ---------------------------- | ------- | ------- | ----------- | ---------- |
| Product prices               | ✔       | ✔       |             |            |
| Product tax class            | ✔       | ✔       |             |            |
| Product status               | ✔       | ✔       |             |            |
| Product visibility           | ✔       | ✔       |             | ✔          |
| Product Inventory            | ✔       |         |             |            |
| Product attributes / transl. | ✔       | ✔       |             | ✔          |  
| Base currency                | ✔       | ✔       |             |            |
| (Default) display currency   | ✔       |         |             | ✔          |
| Category settings            | ✔       |         |             | ✔          |
| System configuration settings| ✔       | ✔       |             | ✔          |
| Root category configuration  |         |         | ✔           |            |
| Orders                       | ✔       |         |             | ✔          |
| Customers                    | ✔       | ✔       |             |            |


### Known issues

#### Resolving URLs to stores
Store resolving may fail if configured secure/unsecure URLs differ, see `\Ho\StoreResolver\Model\StoreUrls::getBaseUrls`,
which only uses the unsecure base URL but should probably check the right one depending on `Request::isSecure()`

## Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](http://keepachangelog.com/) 
and this project adheres to [Semantic Versioning](http://semver.org/).

### [1.0.2] - 2019-02-01
#### Note
- Added support for websites scope
- Add compatability for PHP 7.2
- Fix storeresolver when using multiple websites
- Add compatibility if storegroup has storeviews all with same url

### [1.0.0] - 2017-02-03
#### Note
- Seperated Ho_Multistore and made StoreResolver into own module

### [Unreleased]

## Recent Versions

| Version | Released |
|---|---|
| 1.0.8 | 2025-01-31 |
| 1.0.7 | 2024-01-15 |
| 1.0.6 | 2023-06-20 |
| 1.0.5 | 2022-12-27 |
| 1.0.4 | 2022-08-05 |
| 1.0.3 | 2021-07-14 |
| 1.0.2 | 2021-06-09 |
| 1.0.1 | 2021-06-08 |
| 1.0.0 | 2021-06-04 |
| 0.9.0 | 2021-06-04 |

## Dependencies

### Require

| Package | Constraint |
|---|---|
| php | ~7.3.0\|\|~7.4.0\|\|~8.1.0\|\|^8.2 |

### Replace

| Package | Constraint |
|---|---|
| honl/magento2-storeresolver | self.version |

## Quality

Latest release (1.0.8) fails the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers.


### Compatibility

Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | Pass | Pass | – | – |
| 2.4.8 | – | Pass | 1 | – |
| 2.4.9 | – | – | 1 | 1 |


### Code Quality

Advisory checks against the module's source. Never affect the Compatibility verdict — 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 | 28 | 11 errors, 17 warnings (ruleset: Magento2) — 3 auto-fixable with phpcbf |
| PHPMD | Warning | 13 | 13 rule violations (UnusedFormalParameter:8, MissingImport:3, IfStatementAssignment:1, UnusedLocalVariable:1) |
| Cpd | Pass | 0 |  |
| Composer validate | Info | 2 | valid; 2 advisory notes (composer validate --strict) |

#### PHPStan

Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | 10 | 10 | – | – |
| 2.4.8 | – | 10 | 11 | – |
| 2.4.9 | – | – | 11 | 11 |


### Tests

Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately.

#### 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 | Error | Error | – | – |
| 2.4.8 | – | Error | Error | – |
| 2.4.9 | – | – | Error | not tested |


### Security

Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| Composer audit | Pass | 0 |  |
| Malware scan | Pass | 0 |  |

## Licence and pricing

Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step.

Refundable within 14 days of first purchase via https://packagento.com/account/refunds/.

## Install via Claude Code or any MCP client

The Packagento MCP server can run the licence + project + Composer steps above in one tool call:

```
purchase_and_install_packages(
  composer_names=["ho-nl/magento2-reachdigital_storeresolver"],
  project_id="proj_xxx"
)
```

This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup.

## Vendor

ho-nl is a Magento 2 vendor on Packagento. See https://packagento.com/ho-nl.md for their full catalogue.