PHPackages                             kodexpo/module-scope-override-inspector - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Admin Panels](/categories/admin)
4. /
5. kodexpo/module-scope-override-inspector

ActiveMagento2-module[Admin Panels](/categories/admin)

kodexpo/module-scope-override-inspector
=======================================

Magento 2 admin notices for product, category, and configuration scope overrides.

v1.0.0(1mo ago)02Apache-2.0PHPPHP ^8.1 || ^8.2 || ^8.3 || ^8.4

Since Apr 14Pushed 1mo agoCompare

[ Source](https://github.com/kodexpo/scope-override-inspector)[ Packagist](https://packagist.org/packages/kodexpo/module-scope-override-inspector)[ RSS](/packages/kodexpo-module-scope-override-inspector/feed)WikiDiscussions main Synced 1w ago

READMEChangelog (1)Dependencies (6)Versions (2)Used By (0)

Magento 2 Scope Override Inspector
==================================

[](#magento-2-scope-override-inspector)

`KodeXpo_ScopeOverrideInspector` makes Magento scope overrides visible in admin.

Built by KodeXpo.

Need custom Magento development, admin tooling, or help debugging complex Adobe Commerce backend behavior? Contact: `dev@kodexpo.com`

It shows when lower-scope values on store views or websites still take precedence over parent scope values, directly on:

- product edit pages
- category edit pages
- `Stores > Configuration` section pages

It is designed for teams that work on `All Store Views` for products and categories, on `Default Config` in `Stores > Configuration`, and across multiple scopes, and need clear warnings when saved website or store view values still override what they see or save.

Why This Module Exists
----------------------

[](#why-this-module-exists)

Magento supports `Default Config`, website, and store view scope, but admin users often miss when lower-scope values still override the parent scope.

This module helps by:

- showing override notices on product, category, and config pages
- listing which scope is overriding
- showing which values differ from the parent scope
- linking directly to the overriding scope
- adding store view helper actions to reset visible fields back to default

This is not just a `Use Default Value` fix. It is an admin visibility tool for scope inheritance and override debugging.

Built By KodeXpo
----------------

[](#built-by-kodexpo)

This module is part of KodeXpo's Magento and Adobe Commerce engineering work.

If your team needs:

- custom Magento modules
- admin workflow improvements
- Adobe Commerce backend troubleshooting
- complex scope / configuration debugging

contact `dev@kodexpo.com`

Features
--------

[](#features)

- Product override notices on `All Store Views`
- Category override notices on `All Store Views`
- Config section override notices on `Default Config`, website, and store view scope
- `Store View Overrides` sidebar with grouped details on supported admin edit pages
- Configurable notice layout mode: `Sidebar` (default) or `Inline`
- Direct links to overriding scopes
- Human-readable labels instead of raw config paths where possible
- Store view helper actions:
    - `Check All Use Default`
    - `Check All Use Default And Save`
- Post-save notices when lower-scope values still take precedence
- Included translations:
    - `cs_CZ`
    - `de_DE`
    - `en_US`
    - `es_ES`
    - `fr_FR`
    - `hu_HU`
    - `it_IT`
    - `nl_NL`
    - `pl_PL`
    - `pt_PT`
    - `ro_RO`

Scope Coverage
--------------

[](#scope-coverage)

### Products

[](#products)

On `All Store Views`, the module can show:

- how many store views contain saved values
- how many attributes are saved
- how many attributes actually differ from `All Store Views`
- which store view is overriding
- which attributes differ

Example:

```
Store view overrides exist for this product in 1 store view (8 attributes total, 1 differs from default values).
Store View "Default Store View"
Status: Default Values = "Disabled", Store View = "Enabled". The store view override currently takes priority.

```

### Categories

[](#categories)

The same logic is applied to categories.

Example:

```
Store view overrides exist for this category in 1 store view (1 attribute total, 1 differs from default values).
Store View "Default Store View"
Is Active: Default Values = "Yes", Store View = "No". The store view override currently takes priority.

```

### Store Configuration

[](#store-configuration)

The module checks configuration overrides inside the currently edited configuration section.

It does not rely only on `core_config_data`.

For configuration, the module combines:

- saved rows from `core_config_data`
- effective lower-scope values resolved through Magento config fallback
- values coming from `etc/config.xml` on `default`, `websites`, or `stores` scope when they change the effective value

Behavior by scope:

- on `Default Config`: shows lower-scope overrides from websites and stores
- on website scope: shows values saved on that website and on child store views under that website
- on store view scope: shows values saved directly on that store view

Screenshots
-----------

[](#screenshots)

### Configuration Notices

[](#configuration-notices)

Default Config configuration notice:

[![Configuration Default Config notice](docs/screenshots/config-default-scope.png)](docs/screenshots/config-default-scope.png)

Website scope configuration notice:

[![Configuration website scope notice](docs/screenshots/config-website-scope-2.png)](docs/screenshots/config-website-scope-2.png)

Store view configuration notice:

[![Configuration store view notice](docs/screenshots/config-store-scope.png)](docs/screenshots/config-store-scope.png)

### Category Notices

[](#category-notices)

Category override notice:

[![Category override notice](docs/screenshots/category-default-scope.png)](docs/screenshots/category-default-scope.png)

Category store view helper actions:

[![Category store view helper](docs/screenshots/category-store-scope-helper.png)](docs/screenshots/category-store-scope-helper.png)

### Product Notices

[](#product-notices)

Product override notice:

[![Product override notice](docs/screenshots/product-default-scope.png)](docs/screenshots/product-default-scope.png)

Product store view helper actions:

[![Product store view helper expanded](docs/screenshots/product-store-scope-helper-expanded.png)](docs/screenshots/product-store-scope-helper-expanded.png)

### Display Modes

[](#display-modes)

Inline notice layout on product edit page:

[![Product inline notice layout](docs/screenshots/product-inline-notice-layout.png)](docs/screenshots/product-inline-notice-layout.png)

Notice layout setting in module configuration:

[![Module config notice layout](docs/screenshots/module-config-notice-layout.png)](docs/screenshots/module-config-notice-layout.png)

Store View Helper Actions
-------------------------

[](#store-view-helper-actions)

On product and category store view pages, the module can show two helper actions:

- `Check All Use Default`
- `Check All Use Default And Save`

### Check All Use Default

[](#check-all-use-default)

- checks all available `Use Default Value` checkboxes on the current page context
- does not save automatically

### Check All Use Default And Save

[](#check-all-use-default-and-save)

- checks all available `Use Default Value` checkboxes on the current page context
- asks for confirmation
- triggers the normal save action

Installation
------------

[](#installation)

### Composer

[](#composer)

```
composer require kodexpo/module-scope-override-inspector
bin/magento module:enable KodeXpo_ScopeOverrideInspector
bin/magento setup:upgrade
bin/magento cache:clean
```

If needed:

```
bin/magento setup:di:compile
bin/magento setup:static-content:deploy en_US ro_RO -f
```

### Manual

[](#manual)

Copy the module to:

```
app/code/KodeXpo/ScopeOverrideInspector

```

Then run:

```
bin/magento module:enable KodeXpo_ScopeOverrideInspector
bin/magento setup:upgrade
bin/magento cache:clean
```

Configuration
-------------

[](#configuration)

The module can be enabled or disabled from:

```
Stores > Configuration > KodeXpo > Scope Override Inspector > General > Enable Scope Override Inspector

```

When disabled:

- no notice blocks are rendered
- no post-save notice markers are recorded
- the module remains installed but passive

Notice layout mode:

- `Sidebar` (default): renders scope overrides in a right sidebar panel
- `Inline`: renders scope overrides as the original inline admin notice block

Compatibility
-------------

[](#compatibility)

Designed for Magento Open Source / Adobe Commerce 2.4.5 to 2.4.9 style admin APIs.

Package requirements currently allow:

- PHP 8.1
- PHP 8.2
- PHP 8.3
- PHP 8.4

Limitations
-----------

[](#limitations)

- Product and category reset actions affect available admin fields with a `Use Default Value` checkbox in the current page context.
- Hidden or technical store view rows can still exist in the database even when all available fields already use default.
- Configuration notices currently report lower-scope values but do not provide a bulk reset action similar to product/category pages.

Compared To Other Scope Fixes
-----------------------------

[](#compared-to-other-scope-fixes)

Most Magento scope-related fixes focus on a single issue, usually `Use Default Value` behavior on product forms.

`ScopeOverrideInspector` is broader:

- it covers products, categories, and system configuration
- it highlights real lower-scope precedence issues
- it helps admins navigate and reset overrides instead of only fixing one UI bug

Development
-----------

[](#development)

Run unit tests:

```
vendor/bin/phpunit -c Test/Unit/phpunit.xml.dist
```

Support
-------

[](#support)

For custom Magento development, consulting, or implementation help related to this module, contact:

`dev@kodexpo.com`

License
-------

[](#license)

This module is licensed under the Apache License, Version 2.0. See [LICENSE.txt](LICENSE.txt) for details.

###  Health Score

39

—

LowBetter than 84% of packages

Maintenance89

Actively maintained with recent releases

Popularity3

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity51

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

56d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/2297353694ed98e28fd38bd2640963e21cd4709511b85ff19cb0f9d3892fe149?d=identicon)[kodexpo](/maintainers/kodexpo)

---

Top Contributors

[![kodexpo](https://avatars.githubusercontent.com/u/215408362?v=4)](https://github.com/kodexpo "kodexpo (2 commits)")

---

Tags

ecommercemagentomagento2magento2-extensionmagento2-extension-freemagento2-modulemagento2-module-freephpphp8store-configurationsystem-configuration

### Embed Badge

![Health badge](/badges/kodexpo-module-scope-override-inspector/health.svg)

```
[![Health](https://phpackages.com/badges/kodexpo-module-scope-override-inspector/health.svg)](https://phpackages.com/packages/kodexpo-module-scope-override-inspector)
```

###  Alternatives

[mollie/magento2

Mollie Payment Module for Magento 2

1131.8M12](/packages/mollie-magento2)[run-as-root/magento2-prometheus-exporter

Magento2 Prometheus Exporter

68353.9k](/packages/run-as-root-magento2-prometheus-exporter)[mage-os/module-inventory-reservations-grid

Add a grid with the list of inventory reservations.

1512.6k](/packages/mage-os-module-inventory-reservations-grid)[loki/magento2-admin-components

Admin Panel grids and forms created via Loki Components

173.7k7](/packages/loki-magento2-admin-components)[baldwin/magento2-module-url-data-integrity-checker

Magento 2 module which can find potential url related problems in your catalog data

282806.2k](/packages/baldwin-magento2-module-url-data-integrity-checker)[loki/magento2-components

Core module for defining Alpine.js components with advanced AJAX features

1010.0k22](/packages/loki-magento2-components)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)