ppl / module-discovery-filters

ppl/module-discovery-filters

PPL Discovery Filters for Magento 2 with cached facets for category pages, search pages and Search Intelligence integrations.

  • Pawel Pliousnin
magento2-module Compatibility: 2.4.7-2.4.9 Code Quality: Warning Tests: N/A Security: Pass proprietary

PPL Discovery Filters for Magento 2

PPL Discovery Filters adds indexed, configurable category and search filters with cached facets and optional Search Intelligence handoff.

What It Adds

  • Indexed filter definitions and facet counts for category and search pages
  • Configurable presentation for color, size, category, price, availability, layout, position, AJAX, and native-filter replacement
  • Optional neutral event integration with SearchIntelligence

Requirements And Dependencies

  • PHP: >=8.1
  • Magento packages: magento/framework, magento/module-backend, magento/module-catalog, magento/module-catalog-inventory, magento/module-catalog-search, magento/module-config, magento/module-customer, magento/module-eav, magento/module-inventory-sales, magento/module-store
  • PPL packages: ppl/module-hub

Installation

Install the required PPL packages in dependency order. Composer will skip packages that are already installed:

composer require ppl/module-hub ppl/module-discovery-filters
bin/magento module:enable Ppl_Hub Ppl_DiscoveryFilters
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:clean

Manual app/code installation: copy the dependency modules and this module into app/code/Ppl in this order: Ppl/Hub -> Ppl/DiscoveryFilters. Then run the same Magento commands starting with bin/magento module:enable.

First Use

  • Enable Discovery Filters and configure the filter list and presentation.
  • Run the DiscoveryFilters index build or wait for cron.
  • Check Index Status before judging storefront output.

Admin entry: PPL Hub > PPL Discovery Filters.

Integrations And Boundaries

  • Optionally cooperates with Ppl_SearchIntelligence through the neutral ppl_searchintelligence_filter_integration event.
  • Runs standalone for Magento category and search pages without SearchIntelligence.
  • Stable: run the documented PPL release gates (setup:upgrade, di:compile, PHPUnit, SCD, production mode) in your environment before publishing this package.

Localization

The package includes translation CSV files for 12 locales: de_DE, en_US, es_ES, fr_FR, it_IT, ja_JP, nl_NL, pl_PL, pt_BR, ru_RU, tr_TR, zh_CN.

Customer Documentation

Customer-facing User Guides and Marketplace Long Descriptions are maintained outside the Magento module package in the repository-level docs/user_guides and docs/long_descriptions folders. The module package itself intentionally keeps only this technical README plus developer-relevant files.

Support

Support contact: [email protected]. Include the module version, Magento version, enabled PPL companion modules, and the relevant admin or storefront screenshot when reporting an issue.

Changelog

1.2.0

  • Initial release.
  • Added standalone Ppl_DiscoveryFilters module.
  • Added filter index tables, cache type, cron, CLI commands and PPL Hub admin pages.
  • Added manufacturer, color, size, price, category and stock filter support.
  • Added optional Search Intelligence overlay/search integration through a neutral event handoff, without a hard module
    dependency.
  • Hardened release MVP behavior: search fallback candidates are capped, collection/toolbar totals share one result provider, and price filtering exposes only functional min/max fields with instant apply.
  • Added shared filter theme support for category pages, search pages and the Search Intelligence modal filter component.
  • Added ResultSet-aware facet counting and cache-key scoping for Search Intelligence search-page handoff.
  • Added compact overlay/catalog swatch guards and selected filter readability fixes.
Versions
Version Stability QA Status Compatibility Released
1.2.0 stable Pass Magento 2.4.7-2.4.9 Details 2026-07-08 08:52:48

Requires 21

Package Constraint
ext-ctype *
ext-hash *
ext-mbstring *
magento/framework >=103.0.7 <104.0.0
magento/module-backend >=102.0.0 <103.0.0
magento/module-catalog >=104.0.0 <105.0.0
magento/module-catalog-inventory >=100.4.0 <101.0.0
magento/module-catalog-search >=102.0.0 <103.0.0
magento/module-config >=101.2.0 <102.0.0
magento/module-configurable-product >=100.4.0 <101.0.0
magento/module-cron >=100.4.0 <101.0.0
magento/module-customer >=103.0.0 <104.0.0
magento/module-eav >=102.1.0 <103.0.0
magento/module-inventory-sales >=1.2.0 <2.0.0
magento/module-inventory-sales-api >=1.2.0 <2.0.0
magento/module-search >=101.1.0 <102.0.0
magento/module-store >=101.1.0 <102.0.0
php >=8.1
ppl/module-hub ^1.2
psr/log ^1.0 || ^2.0 || ^3.0
symfony/console ^6.4 || ^7.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.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

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.

Static analysis results
Tool Status Findings Summary
PHPCS Warning 1 1 warning (ruleset: Magento2), 1 auto-fixable with phpcbf
PHPMD Warning 2 2 rule violations (UnusedFormalParameter:2)
Cpd Warning 2 2 duplicated chunks spanning 37 total lines (min-lines=5, min-tokens=70)
Composer validate Info 1 valid; 1 advisory note (composer validate --strict)

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.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

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

Unit tests results by Magento and PHP version
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

Integration tests results by Magento and PHP version
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.

Security results
Tool Status Findings Summary
Composer audit N/A 0 no resolvable dependency tree to audit: Your requirements could not be resolved to an installable set of packages. Problem 1
Malware scan Pass 0
License
proprietary
Authors
  • Pawel Pliousnin — Developer

More from Pawel Pliousnin Digital Solutions

View vendor
Make it pay

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.