symfonysi / magento2-sl-si
symfonysi/magento2-sl-si
Slovenian (Slovenia) language package for Magento 2
Magento 2 Slovenian translations
Slovenian (Slovenia) - sl_SI translations for Magento
Community Edition 2.x.
Translations follow Slovenian grammar and translation rules from
Lugos.
Installation
Option 1: Composer
To install this language package with Composer, run
the following in your Magento 2 root folder:
composer require symfonysi/magento2-sl-si
bin/magento setup:static-content:deploy sl_SI
bin/magento cache:clean
bin/magento setup:upgrade
bin/magento cache:flush
Option 2: Manual installation
Download the ZIP file of the latest available release and extract
it to your Magento root folder at app/i18n/SymfonySi/sl_SI. Also don't forget
to deploy static files for the locale, run the upgrade setup script and cleaning
cache:
bin/magento setup:static-content:deploy sl_SI
bin/magento cache:clean
bin/magento setup:upgrade
bin/magento cache:flush
See also
- Magento user guide - Adding a Language
- Translation mechanism in Magento 2
- Magento 1 Slovenian Translations
- Crowdin - Community effort to
centralize Magento translations. Inactive, new target languages are not being
added.
Supported Magento versions
Supported Magento Community Edition 2.2, 2.1, and 2.0 versions:
2.2.1,2.2.02.1.10,2.1.9,2.1.8,2.1.7,2.1.6,2.1.5,2.1.4,2.1.3,2.1.2,2.1.1,2.1.02.0.4,2.0.3,2.0.2,2.0.1,2.0.0
Contributing and License
Project is open sourced and contributors are welcome. Please check the
contributing
document how to help.
This repository is released under the Open Software License v. 3.0.
Changelog
All notable changes to this project will be documented in this file. This project
keeps a CHANGELOG and adheres to
Semantic Versioning.
[UNREALEASED] - 2017-01-01
- ...
[1.0.5] - 2017-11-16
- Translations for Magento 2.2.1 and 2.1.10
[1.0.4] - 2017-10-24
- Updated translations for current Magento 2 versions and added support for
Magento 2.2.0 - Loosened Magento version restrictions in composer.json
- Fixed
VAT numbertranslation (Dean Podgornik)
[1.0.3] - 2017-06-07
- Support for Magento 2.1.7
[1.0.2] - 2017-05-19
- Repository location renamed
- Packagist namespace renamed because of Magento Marketplace limitations
- Support for Magento 2.1.6
[1.0.1] - 2017-02-28
- Support for Magento 2.1.3, 2.1.2, 2.1.1 and 2.1.0 versions
- Simplified development
- Fix for Composer installation
[1.0.0] - 2017-02-27
- Initial development repository structure
- Initial Slovenian translations for Magento 2.1 and Magento 2.0
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.0.5 | stable | Pass | Magento 2.4.7-2.4.9 Details | 2017-11-16 01:41:11 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2017-10-24 02:10:39 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2017-06-07 01:56:15 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2017-05-19 14:08:33 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2017-02-28 04:51:33 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2017-02-27 01:16:45 |
Requires 1
| Package | Constraint |
|---|---|
| magento/framework | >=100 |
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.
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
| 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
| 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.
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.