elgentos / module-baseurlpath
elgentos/module-baseurlpath
Allow Magento config to have a base url path instead of root without moving Magento 2 into a subdirectory
Magento 2 - Elgentos_BaseUrlPath
Allow setting up a base url in system config other than root.
If you want to add https://my.domain.tld/mypseronalurl/ after the baseurl Magento currently doesn't allow this.
You are left with adding the storecode to the path or creating subdirectories with extra files.
This can get ugly if you just want to add language codes(other than locale-codes) to your domain,
for example https://my.domain.tld/en/ and https://my.domain.tld/nl/
Installation: part 1 - Module via composer
Install the module via composer by running
composer require elgentos/module-baseurlpath
bin/magento module:enable Elgentos_BaseUrlPath
bin/magento cache:flush
Installation: part 2 - Nginx MAGE_RUN_CODE
Make sure you setup your MAGE_RUN_CODE mapping correctly. By default in Nginx this is only done based on $host name.
We will add the $request_uri to the mapping.
# https://{host}/{language}/{magento_request}/
# Most specific match goes first
map $host$request_uri $mageRunCode {
hostnames;
default default;
~other.domain.tld/nl/ other_nl;
~other.domain.tld other_en;
~my.domain.tld/en/ site_en;
~my.domain.tld site_nl;
}
# fastcgi section
fastcgi_param MAGE_RUN_CODE $mageRunCode;
Nginx without mapping
Or if Nginx mapping isn't available for you.
# https://{host}/{language}/{magento_request}/
# Most specific match goes last
# this one is untested thought(sorry for that)
set $mageRunCode "default";
if ($host$request_uri ~ other.domain.tld/) {
set $mageRunCode "other_en";
}
if ($host$request_uri ~ other.domain.tld/nl/) {
set $mageRunCode "other_nl";
}
if ($host$request_uri ~ my.domain.tld/) {
set $mageRunCode "site_nl";
}
if ($host$request_uri ~ my.domain.tld/en/) {
set $mageRunCode "site_en";
}
Configuration
After installation goto Stores / Configuration -> General / Web -> Base URLs ((Un)Secure)
My strong advise setting these settings on website or store view level
because making errors could potentially lock you out from the admin pages
Store 1: site_en
Update your base url to https://my.domain.tld/en/
[image: example baseurl setting english store]
Store 2: site_nl
Update your base url to https://my.domain.tld/nl/
[image: example baseurl setting dutch store]
Static content and media
To make static content work with these settings, you explicitly need to setup these paths to the root(/) of your site.
[image: example baseurl setting static media parameters]
Authors
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 2
| Package | Constraint |
|---|---|
| magento/framework | * |
| magento/module-store | * |
Requires-dev 1
| Package | Constraint |
|---|---|
| phpunit/phpunit | ~6.5.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.
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 elgentos
View vendorLink existing guest orders to newly created or existing customer based on e-mail address
Allows customers to enter a secondary email address to login with
Hide Mollie payment methods based on category
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.