Magento 2 Base Module (Required Library)

What you get

Key Features

Shared Admin Foundation

• Unified admin menu — all Panth extensions appear under a single Panth Infotech sidebar entry
• Centralized configuration — every Panth extension's settings live under Stores → Configuration → Panth Extensions
• Core Settings section — global toggles for debug mode, caching, and module status

Developer Utilities

• Panth\Core\Helper\Theme — detect whether the current store is running Hyva or Luma (used by 30+ Panth extensions to switch templates)
• Panth\Core\ViewModel\ThemeConfig — inject theme tokens into frontend templates
• Panth\Core\Api\ThemeBuildExecutorInterface — optional contract for triggering theme builds from admin

Quality of Life

• Grid data-provider fix — patches the well-known Magento bug where SearchResult virtual types return null from getCustomAttributes() in developer mode
• Cron heartbeat — lightweight cron job that records last-run timestamps for diagnostics (with admin opt-out)
• Module registry — declarative panth_modules.xml lists every installed Panth extension for the overview page

Security & Performance

• MEQP compliant — passes Adobe's Magento Extension Quality Program with zero severity-10 violations
• Zero dependencies on third-party libraries — uses only Magento framework classes
• Lightweight — under 50 PHP files, minimal memory footprint
• Composer-installable — no manual file copying required

What's Inside

Panth_Core/
├── Api/
│ ├── ThemeBuildExecutorInterface.php # Optional contract for theme builds
│ └── Data/
├── Block/
│ └── Adminhtml/ # Admin block helpers
├── Controller/
│ └── Adminhtml/ # Admin controllers
├── Cron/
│ └── Heartbeat.php # Lightweight diagnostics cron
├── Helper/
│ ├── Data.php # General config helper
│ └── Theme.php # Hyva/Luma theme detection
├── Model/
│ ├── Config/ # Configuration sources and backends
│ └── ModuleRegistry.php # Reads panth_modules.xml
├── Observer/ # Event observers
├── Plugin/
│ └── GridDataProvider.php # Magento grid bug fix
├── Service/ # Reusable services
├── Setup/
│ └── Patch/Data/ # Data patches
├── ViewModel/
│ └── ThemeConfig.php # Frontend theme config injector
├── etc/
│ ├── adminhtml/
│ │ ├── menu.xml # "Panth Infotech" sidebar entry
│ │ ├── routes.xml
│ │ └── system.xml # Core Settings config UI
│ ├── crontab.xml
│ ├── di.xml
│ ├── module.xml
│ └── panth_modules.xml # Module registry
└── view/
 ├── adminhtml/
 └── frontend/

Theme Detection

Panth Core's theme detection logic checks multiple signals to reliably identify whether the storefront is running Hyva or Luma:

1. Module check — is Hyva_Theme enabled?
2. Theme path check — does the active theme's path explicitly contain a Luma marker?
3. Parent theme check — does the theme's parent chain include Hyva/default?

This multi-signal approach correctly handles edge cases like:

• Hyva child themes
• Luma child themes
• Mixed installations where Hyva module exists but a Luma theme is active
• Custom themes with non-standard parent chains

The result is cached per-request via $cachedThemeType to avoid repeated database lookups.

Module Registry

The etc/panth_modules.xml file declares every Panth extension installed on the store. Each Panth extension contributes its own entry through DI configuration:

<config>
 <module name="Panth_AdvancedSEO" version="1.0.0">
 <label>Advanced SEO</label>
 <description>Enterprise-grade SEO suite</description>
 <admin_url>panth_seo/dashboard/index</admin_url>
 </module>
</config>

The registry is consumed by the Panth Infotech admin overview page, which displays installed extensions, their versions, and links to their config sections. This gives merchants a single dashboard to see and manage all Panth extensions.

Cron Heartbeat

Panth Core registers a lightweight cron job (panth_core_heartbeat) that runs every hour and records the last execution timestamp. This is useful for:

• Diagnostics — confirming cron is running
• Health checks — external monitoring tools can read the timestamp
• Telemetry opt-in — anonymous module-version tracking (off by default, requires explicit admin opt-in)

To disable the heartbeat entirely, set Cron Heartbeat to No in Core Settings.

Grid Bug Fix

A well-known Magento bug causes admin grids to crash in developer mode when virtual types extending SearchResult return null from getCustomAttributes(). Panth Core ships a plugin (Panth\Core\Plugin\GridDataProvider) that patches this by returning an empty array instead of null.

This fix is applied silently and only affects grids that would otherwise throw errors. It does not modify any product data or alter grid behaviour in production mode.

Troubleshooting

For other issues, enable Debug Mode in Core Settings and check var/log/panth_core.log for detailed output.

Compatibility

Tested on:

• Magento 2.4.8-p4 with PHP 8.4
• Magento 2.4.7 with PHP 8.3
• Magento 2.4.6 with PHP 8.2

Installation

Composer Installation (Recommended)

composer require mage2kishan/module-core
bin/magento module:enable Panth_Core
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush

Manual Installation via ZIP

1. Download the latest release ZIP from Packagist or the Adobe Commerce Marketplace
2. Extract the contents to app/code/Panth/Core/ in your Magento installation
3. Run the same commands as above starting from bin/magento module:enable Panth_Core

Verify Installation

bin/magento module:status Panth_Core
# Expected output: Module is enabled

After installation, navigate to:

Admin → Stores → Configuration → Panth Extensions → Core Settings

Configuration

Panth Core ships with sensible defaults and requires no configuration to function. The following optional settings are available at Stores → Configuration → Panth Extensions → Core Settings:

Compatibility with Other Panth Extensions

Panth Core is the required dependency for all Panth Infotech extensions. Composer handles this automatically — when you install any Panth extension, Core is pulled in.

All Panth Extensions That Require Core

License

Panth Core is free under a proprietary license — see LICENSE.txt. You may install and use it on any number of Magento installations as the required dependency for other Panth extensions.

API Reference

Panth\Core\Helper\Theme

Detect the current frontend theme.

use Panth\Core\Helper\Theme;

class MyBlock extends \Magento\Framework\View\Element\Template
{
 public function __construct(
 Context $context,
 private readonly Theme $themeHelper,
 array $data = []
 ) {
 parent::__construct($context, $data);
 }

 public function isHyvaActive(): bool
 {
 return $this->themeHelper->isHyva();
 }

 public function isLumaActive(): bool
 {
 return $this->themeHelper->isLuma();
 }

 public function getCurrentThemeType(): string
 {
 // Returns 'hyva' or 'luma'
 return $this->themeHelper->getCurrentTheme();
 }
}

Panth\Core\ViewModel\ThemeConfig

Inject theme tokens into frontend templates via layout XML.

<block class="Magento\Framework\View\Element\Template"
 name="my.block"
 template="MyVendor_MyModule::template.phtml">
 <arguments>
 <argument name="view_model" xsi:type="object">
 Panth\Core\ViewModel\ThemeConfig
 </argument>
 </arguments>
</block>

// In template.phtml
$viewModel = $block->getViewModel();
$primary = $viewModel->getColor('primary');
$radius = $viewModel->getRadius('default');

Panth\Core\Api\ThemeBuildExecutorInterface

Optional contract for triggering theme rebuilds from admin. Default implementation returns a friendly "module not installed" payload. If Panth_ThemeCustomizer is installed, it overrides this with the real build executor.

use Panth\Core\Api\ThemeBuildExecutorInterface;

class MyController
{
 public function __construct(
 private readonly ThemeBuildExecutorInterface $themeBuilder
 ) {}

 public function execute()
 {
 $result = $this->themeBuilder->build();
 // $result['success'], $result['message'], $result['output']
 }
}