berrypath / magento2-berrypath-flow-hyva-compat
BerryPath guided selling flows for Magento 2 Hyvä storefronts.
BerryPath Guided Selling Flows for Magento 2 Hyvä
[image: BerryPath Guided Selling Flows for Magento 2 Hyvä]
Bring BerryPath guided selling flows to Magento 2 Hyvä category pages, product pages, and CMS content with responsive, Tailwind-based storefront templates.
This companion package works with berrypath/magento2-berrypath-flow. It uses the same Magento configuration and BerryPath Flow UUIDs; no second integration setup is required.
New to BerryPath? A free plan is available with 1 guided selling flow and up to 2,500 products. Existing customers keep using their current plan.
Built for Magento 2 Hyvä storefronts
- Replaces the standard BerryPath frontend templates through Hyvä's compatibility fallback.
- Supports category, product, and CMS widget placements.
- Supports popup, sidebar, and inline guided selling flows.
- Preserves market, locale, product identifier, and assisted conversion behavior from the main module.
- Uses responsive Tailwind utility classes for banners, buttons, and inline flow containers.
- Keeps the stable
berrypath-flow-widgetCSS classes for integrations and custom styling.
Requirements
- PHP 8.1 or newer.
berrypath/magento2-berrypath-flow.hyva-themes/magento2-compat-module-fallback.- A Magento 2 Hyvä storefront.
Composer installs the main BerryPath module and Hyvä compatibility fallback as package dependencies.
Installation
composer require berrypath/magento2-berrypath-flow-hyva-compat
bin/magento module:enable BerryPath_Flow BerryPath_FlowHyvaCompat
bin/magento setup:upgrade
bin/magento cache:flush
For local app/code development, place the module at:
app/code/BerryPath/FlowHyvaCompat
Rebuild the Hyvä theme CSS after installation when the storefront uses a production Tailwind build.
Configuration
This compatibility package adds no separate admin settings. Configure guided selling flows through the main Magento module:
Store defaults: Stores > Configuration > BerryPath > Flow
Category: Catalog > Categories > BerryPath Flow
Product: Catalog > Products > BerryPath Flow
CMS: Content > Widgets > Add Widget > BerryPath Flow
Add the BerryPath Flow UUID or published widget URL to the desired placement. The Hyvä templates automatically use the configured display type, content, locale, market, and product identifier.
Template compatibility
The module registers this mapping with Hyva\CompatModuleFallback\Model\CompatModuleRegistry:
BerryPath_Flow → BerryPath_FlowHyvaCompat
Compatible templates are included for:
category.phtmlproduct.phtmlwidget.phtml
Tailwind content sources are declared under view/frontend/tailwind/ so the module's template classes can be included in a Hyvä CSS build.
Screenshots
Ask relevant, easy-to-answer questions:
[image: Guided selling question]
Turn shopper answers into focused product recommendations:
[image: Guided selling recommendations]
Use the same guided selling placements across Magento 2 Hyvä content, category, and product pages:
[image: Homepage CMS widget]
[image: Category page widget]
[image: Product page widget]
License
MIT. See LICENSE.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 3
| Package | Constraint |
|---|---|
| berrypath/magento2-berrypath-flow | * |
| hyva-themes/magento2-compat-module-fallback | * |
| 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.
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.
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.
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
| 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
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.
More from berrypath
View vendorTurn 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.