amasty / module-xsearch-porto

amasty/module-xsearch-porto

Advanced Search Porto Compatibility By Amasty

magento2-module Compatibility: Not yet tested Code Quality: Fail Tests: N/A Security: Pass proprietary

module-xsearch-porto

Amasty Advanced Search Compatibility for Porto Theme

Note: This free solution adds partial/basic compatibility between Amasty Advanced Search and the Porto theme for Magento.

The module was created to address known issues that may occur when Amasty Advanced Search is used with Porto theme headers. It improves the search popup behavior and helps display search result blocks correctly inside the popup.

The module adds a new Amasty Advanced Search option to the Porto header search settings. This option should be selected to enable compatibility between Amasty Advanced Search and the Porto theme.

Currently, this solution provides partial compatibility. Some Porto header types and theme configurations may still require additional styling adjustments.


Installation

Run the following commands:

composer require amasty/module-advanced-search-porto
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy <your_locale>
php bin/magento cache:flush

See more details in the Composer User Guide.


Usage

  1. Open the Porto theme settings used for the header search configuration:
    Porto → Settings Panel → Header → Search Type

  2. Select the Amasty Advanced Search option.
    This option must be enabled for the compatibility module to work correctly.

  3. Go to the Advanced Search general settings:
    Stores → Configuration → Extensions → Advanced Search

  4. In the General Settings section, find Search Field Width and set it to Default to avoid header layout issues.

  5. Save the configuration and clear the Magento cache.


Example: Enabling Amasty Advanced Search in Porto

  1. Open the Porto header configuration section:
    Porto → Settings Panel → Header

  2. Find the Search Type setting and select:
    Amasty Advanced Search

Image
  1. Go to the Advanced Search module general settings, locate the Search Field Width setting, and set it to:
    Default
Image

Known Limitations

The following functionality is not fully supported:

  • Popup Width (px) may not work with all Porto header types.
  • Fullscreen Mode is not supported.
  • Custom Search Field Width values are not supported.
  • Some Porto themes or header types may display incorrect popup sizes, colors, or widths.

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
1.0.0 stable Pass Not yet tested Details 2026-06-12 11:46:28

Requires 3

Package Constraint
amasty/base >=1.21.3
amasty/xsearch >=1.22.0
php >=8.1

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 not tested not tested
2.4.8 not tested not tested
2.4.9 not tested not tested

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 4 4 warnings (ruleset: Magento2)
PHPMD Warning 1 1 rule violation (IfStatementAssignment:1)
Cpd Pass 0
Composer validate Info 3 valid; 3 advisory notes (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. Cell → details modal.

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

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
Homepage
https://amasty.com/

More from amasty

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.