elgentos / magento2-alternate-urls

elgentos/magento2-alternate-urls

Add alternate URLs (hreflang) to all pages in the webshop

magento2-module Compatibility: 2.4.7-2.4.9 Code Quality: Warning Tests: N/A Security: Pass proprietary

Magento 2 Alternate URLs

Makes it possible to configure and add alternate URLs to the <head> of each page.
The link to other websites/stores can be created manually in the admin

Installation

This package can be installed using Composer.

composer require elgentos/magento2-alternate-urls
bin/magento module:enable Elgentos_AlternateUrls
bin/magento setup:upgrade

Usage

To use the module, you'll have to enable the module and add some mapping to
"connect" websites/stores to each other. The script will automatically add
references to the <head> of the page for each link that is found for the current
page.

Extending for other page types

To extend this functionality to other page types (like blog posts from a module),
you will have to create a custom module and add a custom type that implements
Elgentos\AlternateUrls\Type\TypeInterface. After that you'll need to add your
custom type to the typeInstances in the alternate_urls block in default.xml.

Example

<?xml version="1.0"?>
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
    <body>
        <referenceBlock name="alternate_urls">
            <arguments>
                <argument name="typeInstances" xsi:type="array">
                    <item name="custom_page_type" xsi:type="object">
                        MyNamespace\CustomPageTypeAlternateUrls\Type\CustomPageType
                    </item>
                </argument>
            </arguments>
        </referenceBlock>
    </body>
</page>

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

proprietary

Changelog

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.2.1] - 2023-05-23

Fixed

  • Solve coding standard errors

1.2.0 - 2022-08-22

Added

  • PHP 8.1 and Magento 2.4.4 compatible

1.1.1 - 2022-08-22

Fixed

  • Solve issue with incorrect multistore category URLs

1.1.0 - 2022-02-03

Added

  • Implement compatibility with Magento 2.3.7-p1

1.0.0 - 2021-11-09

Added

  • Implement alternate URLS for product pages
  • Implement alternate URLS for category pages
  • Implement alternate URLS for CMS pages
  • Implement alternate URLS for default pages (i.e. account pages)
Versions
Version Stability QA Status Compatibility Released
1.2.1 stable Pass Magento 2.4.7-2.4.9 Details 2023-05-23 06:44:53
1.2.0 stable Not tested Not yet tested Details 2023-05-23 06:42:20
1.1.1 stable Not tested Not yet tested Details 2022-08-22 14:47:41
1.0.0 stable Not tested Not yet tested Details 2021-11-09 12:47:40

Requires 3

Package Constraint
php ^7.4||^8.0
magento/framework ^102.0.7||^103.0
magento/module-catalog ^103.0.7||^104.0

Requires-dev 2

Package Constraint
youwe/coding-standard-magento2 ^2.0.0
youwe/testing-suite ^2.9

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.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

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.

Static analysis results
Tool Status Findings Summary
PHPCS Warning 15 15 warnings (ruleset: Magento2) — 1 auto-fixable with phpcbf
PHPMD Pass 0
Cpd Pass 0
Composer validate Pass 0

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.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

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

Unit tests results by Magento and PHP version
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

Integration tests results by Magento and PHP version
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.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
proprietary

More from elgentos

View vendor
Make it pay

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.