Reach Digital Store Resolver

Changelog

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

Installation

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

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

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()

Change Log

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

The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.

[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]