# amasty/module-xsearch-porto > Advanced Search Porto Compatibility By Amasty `composer require amasty/module-xsearch-porto` Canonical URL: https://packagento.com/amasty/module-xsearch-porto ## At a glance - **Vendor**: amasty (https://packagento.com/amasty.md) - **Latest version**: 1.0.0 — released 2026-06-12 - **Pricing**: Free - **Package type**: Magento 2 module - **Status**: active, accepting new buyers ## Installation Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them. 1. **Sign in or create an account** at https://packagento.com/customer/account/. 2. **Add the package to your account.** Open https://packagento.com/amasty/module-xsearch-porto and complete the free checkout. A licence is minted automatically. 3. **Create or pick a project, then activate the licence on it.** - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/. - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project. 4. **Add the project credentials to your Magento codebase.** Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`: ```json { "http-basic": { "packagento.com": { "username": "ppk_live_...", "password": "psk_live_..." } } } ``` Add the Packagento Composer repository to `composer.json`: ```json { "repositories": [ { "type": "composer", "url": "https://packagento.com" } ] } ``` 5. **Install and apply.** ```bash composer require amasty/module-xsearch-porto:* bin/magento setup:upgrade bin/magento setup:di:compile bin/magento cache:flush ``` ## What it does Advanced Search Porto Compatibility By Amasty ## README ## 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: ```bash 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 php bin/magento cache:flush ``` See more details in the [Composer User Guide](https://amasty.com/docs/doku.php?id=magento_2: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 4. 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. ## Recent Versions | Version | Released | |---|---| | 1.0.0 | 2026-06-12 | ## Dependencies ### Require | Package | Constraint | |---|---| | amasty/base | >=1.21.3 | | amasty/xsearch | >=1.22.0 | | php | >=8.1 | ## Quality Latest release (1.0.0) passes the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers. ### Compatibility Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`. | 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. Never affect the Compatibility verdict — 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 | 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 against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases. | 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 per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately. #### 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 | #### Integration 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 Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright. | 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 | | ## Licence and pricing Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step. Refundable within 14 days of first purchase via https://packagento.com/account/refunds/. ## Install via Claude Code or any MCP client The Packagento MCP server can run the licence + project + Composer steps above in one tool call: ``` purchase_and_install_packages( composer_names=["amasty/module-xsearch-porto"], project_id="proj_xxx" ) ``` This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup. ## Vendor amasty is a Magento 2 vendor on Packagento. See https://packagento.com/amasty.md for their full catalogue.