Magento Open Source language pack installation

A Torevo language pack translates the Magento Open Source system interface: storefront, checkout, customer account, system emails and administration. It is a Composer package of type magento2-language. It creates no Torevo account and connects the store to no external service.

The Magento language catalogue lists each package’s locale, exact tested versions and links to its purchase page and PDF guide. Purchase through Adobe Commerce Marketplace. The guide supplied with the specific purchased release takes precedence over the general example on this page.

Compatibility and scope

At the review on 30 September 2026, the published packages were version 1.0.0:

Packages	Tested Magento Open Source
Arabic (ar_SA)	2.4.9
Other catalogued languages	2.4.7-p10, 2.4.8-p5, 2.4.9

Always confirm current scope on the specific Marketplace page. The Adobe system requirements list PHP 8.5 for Magento 2.4.9, PHP 8.3 or 8.4 for 2.4.8, and PHP 8.2 or 8.3 for 2.4.7.

Apply current security fixes for your release line. The version number 2.4.9 alone does not confirm that they are installed. Adobe’s September security update requires earlier monthly patches and a separate CVE-2026-75650 hotfix. A language pack installs none of these fixes. The store administrator verifies patch status.

The package does not automatically translate products, categories, CMS pages, blocks or custom email content. Themes and extensions can use their own dictionaries. Adobe Commerce-exclusive modules, Hyvä, PWA and headless storefronts need separate verification. Arabic and Hebrew do not supply RTL layouts or fonts by themselves.

Before installation

Prepare file and database backups, a staging environment, the exact Magento and PHP versions, Composer access and permission to run Magento CLI as the application file-system owner. Confirm the package name and locale in the purchased PDF.

Use the Marketplace account that purchased the package and its access to repo.magento.com. Store public and private Composer keys in secure authentication configuration, never in a public repository, screenshot or support message. Adobe documents Composer package installation.

Run the following commands individually from the Magento application root. The example uses the Polish package torevo/language-pl-pl, locale pl_PL and store-view code default. Replace both the package name and locale for another language. A store-view code is separate from the locale. Use the code returned by store:list.

1. Install the package and identify the mode

composer require torevo/language-pl-pl:1.0.0
php bin/magento setup:upgrade
php bin/magento deploy:mode:show
php bin/magento store:list

Composer must complete without errors and install the purchased package. For an authentication error or missing package, check the Marketplace account, access keys, repository and component name shown with the purchase.

Test the entire workflow on staging first. Deploy to production in a scheduled maintenance window through the existing release process. Enable maintenance before changing dependencies. A language pack is not a module, so do not use module:enable for it.

2. Configure the store-view language

Default or developer mode

In Admin, open Stores → Settings → Configuration. Select the required store view in Scope. Under General → General → Locale Options, clear Use Website next to Locale, choose the locale and save.

php bin/magento setup:static-content:deploy -f en_US pl_PL
php bin/magento cache:flush

If Locale and Use Website are disabled, check the application mode and any configuration lock. Use the CLI workflow for production mode.

Production mode

Production mode can display Locale and Use Website as disabled controls. Use the CLI workflow in the package guide. Do not switch the store to developer mode just to change its language.

php bin/magento maintenance:enable
php bin/magento config:set --scope=stores --scope-code=default general/locale/code pl_PL
php bin/magento setup:static-content:deploy -f en_US pl_PL
php bin/magento cache:flush
php bin/magento config:show --scope=stores --scope-code=default general/locale/code

The final command must return pl_PL. The example generates English and Polish static files, including Admin assets. Keep all active locales in a multilingual deployment. Use the same release artifact and configuration across multiple nodes.

If configuration is managed through config.php, env.php or a cloud deployment, align the change with that process. Do not overwrite an existing lock without its owner. Adobe documents scope and config:set.

After successful deployment and verification, restore normal operation:

php bin/magento maintenance:disable

If a command fails, resolve the cause or restore the previous release first. Do not reopen the store with an incomplete deployment.

3. Configure the Admin account language

Storefront and Admin language settings are separate. Once static files for the locale are deployed, the administrator opens Account Setting, changes Interface Locale and saves after confirming with their own password. Enter that password only into Magento, never send it to Torevo support.

4. Verify the result

In a fresh browser session, check:

• navigation, category, search and product,
• cart, shipping, payment, validation and test-order confirmation,
• registration, sign-in, addresses and customer account,
• order, invoice and shipment system emails,
• administration, JavaScript wording, caches and custom extensions.

Missing translations in a custom theme can come from its dictionary, inline translations or an extension-specific phrase. Do not edit files in vendor/. Use a supported theme or module dictionary for custom wording.

Updating and uninstalling

Before updating, check the new Marketplace release and your backup. On staging, run composer update torevo/language-pl-pl, review lock-file changes and repeat setup:upgrade, static-content deployment and verification. Deploy the tested release through your production release process.

Before removal, switch affected store views and Admin accounts to a locale that will remain installed. Then run on staging:

composer remove torevo/language-pl-pl
php bin/magento setup:upgrade
php bin/magento cache:flush

Regenerate static content for the remaining locales and test the store. Removing the dictionary does not delete merchant-authored product or CMS content.

Troubleshooting and support

Situation	What to check
Locale cannot be changed in Admin	application mode, configuration lock and the production CLI workflow
Storefront remains in English	correct store-view code, config:show, exact locale deployment and cache
Only some wording is untranslated	theme or extension dictionary, inline translation and merchant content
Arabic or Hebrew wording has the wrong layout	RTL and fonts in the specific theme. The dictionary does not configure them
Composer cannot download the package	purchase account, authentication, repository and exact component name

Contact support@torevo.tech. Include package name and version, locale, Magento and PHP versions, deployment mode, store-view code and redacted error text. Never send Composer keys, passwords, auth.json, env.php or customer data.