avstudnitz / scopehint2
avstudnitz/scopehint2
Displays a hint when a configuration value is overwritten on a lower scope (website or store view).
AvS_ScopeHint for Magento 2
Displays a hint when a configuration value is overwritten on a lower scope (website or store view).
Facts
- extension on GitHub
- direct download link
- Composer key:
avstudnitz/scopehint2(registered at Packagist)
Description
Whenever a configuration setting is overwritten by a lower level website or store view, an icon is displayed.
On Mouseover, a list of all stores / websites which overwrite the setting is shown with the respective values.
See the screenshot to get an impression of what the module does:
[image: Screenshot]
The module also optionally displays the configuration code (which is used for ScopeConfigInterface::getValue()) with the configuration fields.
This is on by default, and can be enabled/disabled in
Stores -> Settings -> Configuration -> Advanced -> Developer -> Debug -> Display path for each option in system configuration
Requirements
- PHP >= 5.6.0
Compatibility
- Magento >= 2.1.0 (not tested on 2.0.x)
Installation Instructions
Via Composer:
- Call
composer require avstudnitz/scopehint2in your Magento root dir from the command line
Via Download
- Copy all the files into the newly created directory
app/code/AvS/ScopeHint/in the Magento 2 root.
In both cases:
- Enable the extension by calling
bin/magento module:enable AvS_ScopeHint. - Run
bin/magento setup:upgrade.
Uninstallation
- Uninstall the extension by calling
bin/magento module:uninstall AvS_ScopeHint. - Remove all extension files from
app/code/AvS/ScopeHint/or use Composer to remove the extension if you have installed it with Composer
Support
If you have any issues with this extension, open an issue on GitHub.
Contribution
Any contribution is highly appreciated. The best way to contribute code is to open a pull request on GitHub.
Developer
Andreas von Studnitz
Licence
OSL - Open Software Licence 3.0
Copyright
(c) 2017-2024 Andreas von Studnitz
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.3.4 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2025-05-05 07:28:52 |
| 1.3.3 | stable | Not tested | Not yet tested Details | 2025-03-10 09:47:23 |
| 1.3.2 | stable | Not tested | Not yet tested Details | 2025-01-27 12:55:38 |
| 1.3.1 | stable | Not tested | Not yet tested Details | 2025-01-15 14:39:07 |
| 1.3.0 | stable | Not tested | Not yet tested Details | 2024-11-28 11:18:19 |
| 1.2.4 | stable | Not tested | Not yet tested Details | 2024-11-28 11:12:56 |
| 1.2.3 | stable | Not tested | Not yet tested Details | 2024-11-26 09:53:49 |
| 1.2.2 | stable | Not tested | Not yet tested Details | 2023-04-06 08:58:48 |
| 1.2.1 | stable | Not tested | Not yet tested Details | 2022-11-07 10:40:39 |
| 1.2.0 | stable | Not tested | Not yet tested Details | 2022-10-17 09:26:43 |
| 1.1.5 | stable | Not tested | Not yet tested Details | 2022-01-14 07:11:55 |
| 1.1.4 | stable | Not tested | Not yet tested Details | 2020-07-30 06:29:43 |
| 1.1.3 | stable | Not tested | Not yet tested Details | 2019-10-18 08:19:12 |
| 1.1.2 | stable | Not tested | Not yet tested Details | 2019-08-19 11:28:50 |
| 1.1.1 | stable | Not tested | Not yet tested Details | 2019-01-25 12:26:40 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2019-01-22 15:43:31 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2019-01-07 14:52:33 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2019-01-07 14:51:13 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2018-11-20 16:00:02 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2017-10-20 09:45:22 |
| 1.0.0-beta.1 | beta | Not tested | Not yet tested Details | 2017-03-03 14:27:42 |
Requires 2
| Package | Constraint |
|---|---|
| magento/framework | ~102.0|~103.0 |
| magento/module-config | ~100.0|~101.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.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Warning | 11 | 11 warnings (ruleset: Magento2) — 5 auto-fixable with phpcbf |
| PHPMD | Warning | 10 | 10 rule violations (IfStatementAssignment:4, UnusedFormalParameter:3, UnusedLocalVariable:1, CyclomaticComplexity:1, NPathComplexity:1) |
| Cpd | Pass | 0 | |
| Composer validate | Pass | 0 |
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 |
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 avstudnitz
View vendorTurn 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.