Guide

Installation

All modules are installed the same way: with Composer, followed by the usual Magento setup commands. The command for a single module is on its page.

Requirements

  • Magento Open Source or Adobe Commerce 2, installed with Composer.
  • Command line access to the Magento root directory, Composer 2 and the PHP version of your store.
  • The Magento and PHP versions listed on the module page. They are taken from the current release on Packagist, including the modules it builds on.

New major versions are developed for Magento 2.4.6 or later and PHP 8.2 or later and released step by step (already released: Core, Foundation). Composer picks the newest release that fits your store, so older stores keep getting the version that works for them.

Try new modules in a development or staging copy of your store first, and keep a backup of code and database before changing the production store.

1. Add the module with Composer

Run this in the Magento root directory, with the package name from the module page:

composer require infrangible/m2-catalog-product-option-badge

Composer also installs the Infrangible modules it builds on (listed under "Builds on" on each module page). All packages are on the public Packagist repository, no extra repository or access key is needed.

2. Enable the new modules

List the modules that are installed but not enabled yet, then enable the Infrangible ones:

bin/magento module:status --disabled
bin/magento module:enable $(bin/magento module:status --disabled | grep '^Infrangible_')

You can also enable the modules one by one: bin/magento module:enable followed by the names from the list.

3. Update the database and code

bin/magento setup:upgrade

In production mode, also compile the code and deploy the static files (with the locales of your store views), and put the store into maintenance mode around these steps:

bin/magento maintenance:enable
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f en_US de_DE
bin/magento maintenance:disable

In developer mode, setup:upgrade is enough.

4. Clear the cache

bin/magento cache:flush

Then look for the new settings in the admin. Most modules add a section under Stores > Configuration; the module page says where.

Hyvä theme

Some modules change the storefront. If your store uses the Hyvä theme, install the Hyvä companion module as well; it is named like the module with -hyva at the end and linked on the module page. Modules that only work in the admin or in the background need no companion.

Updating

composer update 'infrangible/*' --with-dependencies

Then run steps 3 and 4 again. A new major version (for example 2.x to 3.x) can change requirements; check the module page before updating.

Removing a module

Disable the module first (with its name from bin/magento module:status), then remove the package and update the setup:

bin/magento module:disable Infrangible_ModuleName
composer remove infrangible/m2-module-name
bin/magento setup:upgrade
bin/magento cache:flush

Composer refuses to remove a package that other installed modules still need.

Need help with the installation?

We install and configure the modules in your store, or adapt them to your requirements.

Contact us