Venta - Hyvä-Based Premium Template
Support & Updates
Compatibility
Venta Theme builds on Hyvä’s performance foundation and turns it into a complete premium storefront solution. It includes 200+ Figma views, SEO and GDPR compliance extensions, Out-of-Stock notifications, and ElasticSuite search out of the box. With conversion-focused UX patterns, production-ready layouts, and every core Magento page styled, Venta saves months of custom work and helps your store launch faster while scaling with your business.
Venta Theme completely changed our store experience. The speed improvement was immediate, and our Core Web Vitals jumped into the green for the first time. Highly recommended!
We truly enjoy working with Magebit and trust their expertise and guidance!
Magebit has been our partner for years. This project was another piece of cake for them — smooth and successful.
Magebit’s Hyvä solution gave us the speed, design, and user experience we needed. They turned our concerns into confidence.
Venta Theme ships with a complete design system, not just code. You get a Figma kit with 200+ views, covering every core storefront page and edge case in both desktop and mobile. This gives your team a ready-to-use visual foundation, ensuring faster approvals, smoother development, and a consistent customer experience.
The assets are production-ready and can be customized to your brand with ease — colors, typography, imagery, and spacing are all defined through a scalable design system
Venta Theme is delivered as more than just a frontend skin — it's a complete package consisting of:
Bundled extensions:
Venta’s header extends Magento defaults with more flexibility for merchants. It keeps the structure clean while adding configurability for navigation and promotions.
Venta’s footer is designed for flexibility, combining admin settings with CMS blocks for quick updates.
The mini-cart is AJAX-powered and optimized to drive conversions. It updates instantly, keeping the shopping flow smooth.
Venta improves Magento’s compare feature with a cleaner layout and instant interactions.
Mobile navigation is built as a slide-in drawer optimized for smaller screens, balancing usability with merchandising.
Venta simplifies switching between languages and currencies with a lightweight dropdown that avoids clutter.
Venta introduces a curated pre-search panel that opens instantly when the customer clicks into the search bar. It helps merchants guide discovery before typing even begins.
Once a customer starts typing, ElasticSuite-powered autocomplete delivers fast and relevant suggestions. It ensures search becomes a conversion tool instead of a frustration point.
A focused account dropdown tied to the header icon. Logged-out users see exactly two links: “Login” and “Register.” Logged-in users see the full My Account menu (Orders, Addresses, Wishlist, Newsletters, etc.) for quick access — lightweight and consistent with Hyvä.
Venta Theme uses AJAX across core shopping flows to create a faster, smoother experience. With fewer page reloads, shoppers stay engaged and move through the journey with less friction — which supports higher conversions and average order value.
Instantly adds products without page reloads
Updates in real time, shows cross-sells, and displays recently viewed products if empty
Saves items instantly from PDP or category page
Quick product comparison setup without reload
Layered navigation updates products instantly
Switch pages without reload, or use infinite scroll for continuous browsing
Venta’s homepage is designed to be campaign-driven and conversion-focused. It ships with ready-to-use widgets so merchants can quickly build a dynamic storefront without heavy custom work.
Venta makes category browsing clearer and faster, with flexible layouts, a smarter sidebar, CRO-optimized layered navigation, rich product-card interactions, and an improved search results page that never dead-ends.
Venta supports both Grid and List views. Choose what the page shows by default — Products only, Sub-categories only, or Sub-categories + Products (not available in default Magento). Optional bottom SEO content helps rank without clutter.
A redesigned sidebar category tree improves readability and depth handling versus Magento default. Works smoothly with layered navigation.
Instant AJAX updates, clear selected-filter chips, tidy collapsible groups, plus optional attribute descriptions to reduce confusion and increase applies-per-session.
Snappy, informative cards: Hover image change, Configurable options on hover (show one or multiple attributes like color/size), Tier pricing visualization, plus quick actions.
Keep shoppers in flow with AJAX pagination or Infinite scroll where it fits.
Guide discovery and run campaigns with category thumbnails and promo banner slots above or within the grid.
The search results template mirrors category clarity: clean product grid/list, visible sort & filter controls, and selected-filter chips. Empty searches never dead-end — if a user submits with no query (or clears it), the page still returns results like trending products, popular categories, or bestsellers.
Venta’s Product Detail Page is built to reduce friction, keep the primary CTA visible, and help shoppers decide faster, especially on mobile. Key conversion features, like Sticky Add to Cart and image zoom, are configurable from the admin.
A persistent bottom bar appears once the main Add to Cart button is out of view, so shoppers can add to cart without scrolling back up. Works for Simple and Configurable products, syncs with the main form, includes product name, selected options, price, and CTA.
Zoom is built-in and configurable, including maximum zoom level. This is especially useful for detail-heavy products where visuals drive confidence.
You can pin selected attributes directly under the product title, so customers instantly see the specs that matter most, like size, material, compatibility, warranty, shipping class.
Venta lets you add short descriptions for attributes, shown as tooltips in multiple locations. This helps explain what an attribute means, not just its label.
Where to manage it:
Manage Short Description in Product Attribute Configuration.
Attributes can be shown as tabs on the PDP alongside Description and Additional Info, great for “Specs”, “Materials”, “Care”, “Warranty”, “Shipping”.
For richer content, Venta also adds a CMS Block attribute type, you can assign CMS blocks to products (even via mass action) and display them on the frontend, perfect for standardized content across many SKUs.
Venta supports cross-sells in the mini-cart, and includes an option to hide out-of-stock products in cross-sells, upsells, and related products, so recommendations do not look broken.
Venta supports Magento tier pricing on the PDP, so volume discounts are clear for B2B and high-quantity purchasing flows.
Venta’s cart keeps the default Hyvä “all items visible” layout, but makes it feel more polished and easier to scan, so customers can review the order fast and move to checkout with less friction.
Cart interactions stay smooth with AJAX enabled, including remove item and quantity updates, so totals refresh without full reloads.
Add relevant products directly in the cart flow. Venta includes a configurable cross-sell slider in the mini-cart, so you can push extras at the right moment.
If you use tier pricing, the cart reflects volume pricing clearly, so customers understand why the price changes when they increase quantity.
Customers can apply coupon codes directly in the cart, and with AJAX cart actions enabled the cart experience stays lightweight (quick feedback, updated totals, no “heavy” reload feeling).
A simple “Clear cart” option lets customers empty the cart in one action, useful for B2B buyers, quote-driven orders, or shoppers who want to restart.
Venta keeps checkout clean and familiar, matching what shoppers are used to today, so they don’t have to “learn” your store at the most sensitive step. Under the hood it preserves Hyvä Checkout functionality, but adds Venta styling and layout options.
You can switch between Venta One Page (single-page layout) and Venta Default (more traditional flow), plus keep default Hyvä layouts as fallback options.
Run Guest Checkout or require login, depending on your business model. If you want a cleaner flow (no login step at all), you can remove the login step via checkout config.
Reduces hesitation and support tickets, especially for new customers.
Built-in popups for Terms and Conditions, so customers never leave checkout, and can review policies without breaking flow.
Better validation and feedback during checkout, fewer “silent errors”, smoother completion rates.
Checkout is designed to feel great on mobile, clean spacing, readable inputs, and friction-free taps.
After purchase, customers get:
Venta reworks the entire My Account area to feel modern, consistent, and easy to use, not just “styled enough”. It’s part of Venta’s core UI/UX improvements across the store.
Fully redesigned account experience
Including login, registration, and the My Account area, so customers get a clean, consistent UI across the full journey.
You can assign a custom “Status Color” per order status in admin, perfect for “Processing”, “Shipped”, “Delivered”, “Cancelled”, etc.
Everything you can manage without dev work
Below is the full list of Venta Theme admin-level controls (including the ones we mentioned under PDP, Cart, Checkout, My Account, etc.), grouped by area, with the config paths where they live.
Stores → Configuration → Magebit → Theme
Stores → Configuration → Magebit → Cart Actions
Search Suggestions
Stores → Configuration → Magebit → Search Suggestions → General
Layered Navigation
Infinite Scroll
Stores → Configuration → Settings → Magebit → Infinite Scroll
Managed on attribute level in admin
PDP Image Fitting, No "White Bars"
Stores → Configuration → Magebit → Theme → Image Resizer
Managed in category edit screens
Stores → Configuration → Hyva Themes → Checkout
Content → Pages → Select any page
Managed on order status level in admin
Marketing → Communications → Email Templates
Venta does not stop at “core shopping pages”, it also ships with the pages customers hit every day around the buying journey, all styled consistently, with clean UX and no unfinished-looking states.
Venta includes a pre-built Contact Us page template with a clean form and space for the things customers actually need.
Includes:
A ready-to-use About Us template that fits the Venta design system, so you can launch faster and refine content over time without redesigning the page structure.
A styled 404 page that feels like part of the storefront, with clear navigation back to shopping instead of a dead-end experience.
Every “non-happy-path” page is designed and intentional, so customers never see default Magento-looking screens.
Examples:
Venta is built on top of Hyvä, not beside it. Hyvä is the parent theme, and Venta extends it, keeping the architecture clean and aligned with Hyvä best practices.
Venta ships with the Magebit SEO Extension, a practical SEO toolkit that covers the stuff teams typically patch together with multiple plugins, structured data, richer snippets, clean indexation signals, and better social sharing previews. It’s designed to improve discoverability without turning SEO into a dev-only task.
Where it’s managed
Stores → Settings → Configuration → Magebit (store-view level supported)
The extension automatically shows breadcrumbs on all pages except the main landing page, which helps users navigate and also provides structured breadcrumb data to search engines.
Why it matters
Venta includes an FAQ block you can add with Page Builder, and it also outputs the structured FAQ schema so those questions can appear directly in Google results when relevant.
Why it matters
Adds LocalBusiness structured data, so search engines can better understand and display your business details in local search contexts.
Adds hreflang tags to help search engines serve the correct language or regional version of a page.
Why it matters
Canonical Tags (preferred page version)
Canonical tags reduce duplicate content issues and consolidate ranking signals to the “main” version of a page. The docs include quick verification steps (view source, find canonical).
Why it matters
OG Tags + Twitter Cards (social media previews)
Adds and supports configuration of Open Graph and Twitter card metadata, so your pages look consistent when shared across Facebook, LinkedIn, X, etc. It also includes guidance for testing via OG validators and browser extensions.
Why it matters
Apple Touch Icons (iOS bookmarks and home screen)
Defines Apple touch icons for a more “app-like” experience when users save the site on iPhone/iPad.
Why it matters
Generates a clickable HTML sitemap at /sitemap when enabled, useful for users and internal linking structure. Docs also explain how to verify if it’s enabled.
Why it matters
Venta includes the Magebit GDPR Extension, a practical compliance toolkit built for real stores, not just a basic cookie banner. It helps you manage cookie consent properly, keep an audit trail, and give customers clear privacy controls, while staying consistent with the Venta, Hyvä storefront UX.
The extension provides a configurable cookie bar with Accept, Decline, and Custom settings, so customers can manage consent by cookie group, instead of a single yes/no click. Preferences can be updated later using a storefront button, so shoppers stay in control without hunting for a hidden settings page.
What you can customize
Cookies can be organized into groups (like Analytics, Marketing, Functional, Preference), each with its own description and cookie list. This makes consent easier to understand for customers and easier to manage internally.
Admin control
The extension includes Consent Mode V2 configuration, designed to control the default state for Google services and adjust tracking behavior based on the user’s consent choices. This is important for stores that rely on analytics and marketing tools but still want to keep privacy handling clean.
Every consent decision can be stored in a Cookie Consents Log, including consent status, date, and technical data required for compliance auditing. You can also configure retention and auto-cleaning intervals to avoid keeping consent logs longer than needed.
Admin access
Magebit GDPR → Cookie Consents Log
Customers can request account deletion directly from their account area, with clear messaging about timeline, confirmation, and cancellation options. This supports common GDPR expectations around user data control.
If needed, you can add a required checkbox during account creation, ensuring users explicitly agree to your terms as part of the signup flow.
Main configuration
Stores → Settings → Configuration → Magebit
Cookies
Magebit GDPR → Cookies
Cookie groups
Magebit GDPR → Cookie Groups
Consent audit log
Magebit GDPR → Cookie Consents Log
Venta includes the Magebit Tracking Extension, built to make analytics more accurate, faster, and more resilient than classic “just drop a bunch of pixels in the browser” setups. The core idea is server-side tagging, so you collect first-party data, reduce script load in the browser, and keep tracking working even when ad blockers or browser privacy rules get in the way.
Why it matters for merchants
If your tracking is off, you end up making decisions based on incomplete data, campaigns mis-attribute conversions, and you waste budget. The Tracking Extension is designed to solve the common problems: data loss from blockers, buggy events, broken Google Ads attribution, and performance hit from too many client-side scripts.
You can enable tracking for Core Web Vitals metrics, including CLS, LCP, INP, and optionally user engagement events, so you see performance and behavior together.
When using the server-side GTM route, you can enable Enhanced Conversions and send them through the dataLayer for improved ads tracking accuracy.
Clear Magento config area
Stores → Settings → Configuration → Magebit → Tracking
Built-in configuration sections
Testing guidance and process
Including an extended testing guide, plus GTM preview workflow.
Hosting option for server-side GTM
Docs describe using Stape as a practical way to host server-side GTM, including plan considerations for production traffic.
What you actually configure
In Magento you select the tracking method, enter GTM key, choose events, optionally enable CWV and engagement events, enable first-party loading for gtag.js, set the server-side GTM endpoint, configure conversion events in DataLayer, then flush cache.
CSP considerations
If the tagging server is not under the same domain, you may need to allow it via CSP rules, the docs reference using a CSP approach or a dedicated helper extension.
Out-of-stock products are usually dead ends. Venta turns them into future revenue by letting shoppers subscribe to back-in-stock alerts right from the PDP and PLP, then automatically emailing them when the product is available again. It supports both guests and logged-in customers, and it is built on Magento’s native Product Alerts, but with a Venta, Hyvä-optimised UX using Tailwind CSS and AlpineJS.
What customers see on the storefront
Customers get a dedicated My Stock Alerts section where they see all active subscriptions, including variant details, and can unsubscribe per product.
Email notifications that do not annoy customers
Configuration
Stores → Configuration → Magebit → Out Of Stock Notifications
Notifications
Admin dashboards for visibility and cleanup
Marketing → Venta Stock Alerts
Heavy, outdated frontend (Luma-based)
Hyvä-based, Core Web Vitals optimizedNot compatibleFully compatible (Hyvä Theme, Checkout,None provided200+ Figma files/views (desktop & mobile)Often encrypted or bloated100% open source, clean, fully accessibleNone bundledVenta SEO, GDPR, Out-of-Stock NotificationsStandard Magento navigation, limited filtersPre-search, banners in menu, AJAX filters,Default Magento layoutsCRO-optimized PDP with sticky price bar,Default or heavy third-party overridesAJAX mini-cart with cross-sells, fallbackDefault 6-step Magento checkout or customCRO-optimized checkout flow,Requires add-ons or manual setupBuilt-in GDPR & accessibility patternsOften unstyled (404, Contact, empty states)Fully styled 404, Contact Us, About Us,Often fragile with multi-store or enterprise useMulti-store & multi-language ready, AdobeNo. Venta is built on top of Hyvä. You still use Hyvä as the frontend foundation, and Venta adds premium UX, design assets, and bundled extensions.
Other themes are usually Luma-based, slow, or not Hyvä-compatible. Venta is the first premium Hyvä-based theme, optimized for Core Web Vitals, and comes with 200+ Figma files, SEO, GDPR, and Out-of-Stock extensions.
Over 200 desktop and mobile views covering every core storefront page and state — giving your designers and developers a complete reference for build and customization.
Yes. A license includes versioned releases and active updates. Extended support options are available depending on your package.
Absolutely. Venta is designed as a flexible starting point. You can adjust colors, fonts, layouts, and components to fit your brand.
No. Venta is built on Hyvä’s lightweight frontend and optimized for performance. In fact, most merchants see speed and UX improvements compared to default Magento themes.
Yes. Hyvä Theme and Hyvä Checkout licenses are separate purchases. Venta is a premium add-on layer that enhances them.
No. Venta is 100% open source. Your developers have full access to all code.
Yes. Venta is fully compatible with the Hyvä ecosystem, including Hyvä Theme, Hyvä Checkout, Hyvä Commerce, and Hyvä Enterprise.
Yes. Venta works with Magento Open Source, Adobe Commerce (on-premise), and Adobe Commerce Cloud.
Warning Before upgrading Venta Theme on your own, read Updating to Venta Theme 1.7.3.
Magento_Swatches/templates/product/swatch-item.phtml)setup()window so child themes can compose on top of them instead of forking the components (web/tailwind/js/bundle/header.js, web/tailwind/js/bundle/menu.js)customer_menu_links directly through a customer.account.navigation container instead of a second Magento\Customer\Block\Account\Navigation block (Magento_Customer/layout/customer_account.xml)hyva-themes/magento2-hyva-checkout from 1.3.13 to 1.3.14 in root and theme composer.jsonColor: and Size: swatch legends between 768px and 1280px, matching the tablet designinitShowSwatchesIntersect() stub from the swatch options componentcustomer_menu_links.phtml wrapper template that only rendered the customer_menu_links block (Magento_Customer/templates/html/customer_menu_links.phtml)header.customer.logged.in.links link list, bypassed by header/customer-menu.phtml (Magento_Customer/layout/default.xml)customer.header.wishlist.link re-declaration and the template it pointed at (Magento_Wishlist/layout/default.xml, Magento_Wishlist/templates/sortable-item/link.phtml)Magento_Cms/templates/navigation-column.phtml)span and a tags on cart, order success and order view: added span to the order success and order view item renderers, and the allow-list to the cart’s full_view branch (Magento_Checkout/templates/php-cart/item/default.phtml, Magento_Checkout/templates/success/order/items/renderer/default.phtml, Magento_Sales/templates/order/items/renderer/default.phtml)account-stored-payments-link being declared twice, leaving the single sortOrder 30 entry that the layout merge already applied (Magento_Customer/layout/default.xml)customer_menu_links is absent, by guarding the block lookup (Magento_Customer/templates/header/customer-menu.phtml)lg to xl and sizing the 1280px columns to the designMagento_Catalog/templates/product/list/toolbar/sorter.phtml)Magento_Customer/templates/form/register/agreements.phtml), the Hyvä Checkout terms step (Hyva_Checkout/templates/default/checkout/terms-conditions/list.phtml) and the checkout footer agreement links (Hyva_Checkout/templates/default/page/footer/agreement-links.phtml)md and lg on products with no related products (Magento_Catalog/templates/product/product-detail-page.phtml)Magento_Catalog/templates/product/product-detail-page.phtml)Hyva_Checkout/templates/default/checkout/terms-conditions/list.phtml)csv-parse to 7.0.2 in the Playwright lockfile to close the prototype-replacement advisory (GHSA-8cw4-87c7-c6xx)immutable to 3.8.4 in the Tailwind lockfile to close the hash-collision DoS advisory (GHSA-xvcm-6775-5m9r)fast-uri to 3.1.7 and postcss-selector-parser to 7.1.6 in the Tailwind lockfile@faker-js/faker to 10.6.0 in the Playwright lockfilejs-yaml to 4.3.2 and colord to 2.10.0 in the Tailwind lockfile.cms-rich-text shares the [data-content-type='html'] text, list and table styling for CMS content that is not a Page Builder content type (web/tailwind/components/content.css)Warning Before upgrading Venta Theme on your own, read Updating to Venta Theme 1.7.2.
hyva-themes/commerce composer suggest entry in the theme composer.jsonboxtwentytwo/module-cloudflare-turnstile as a suggested packageBoxTwentyTwo_CloudflareTurnstile::hyva/js/script_loader.phtml)Cart\Items view model is gone from Magento_Theme/templates/html/header.phtmlMagento_ReCaptchaFrontendUi::js/script_loader.phtml)window.grecaptcha, which Turnstile’s compat mode also definesMagento_Newsletter/templates/subscribe.phtml)hyva-themes/magento2-hyva-checkout from 1.3.12 to 1.3.13 in root and theme composer.json.shimmer-shine-sm styles from shimmer.cssMagento_Theme/templates/html/footer.phtml)x-spread with x-bind in cart-drawer.phtmlpageshow state resets to the customer menu, authentication popup, and messages components so pages restored from bfcache do not show stale statepageshow reset for the mobile menu stores in menu.js so a page restored from bfcache does not keep the menu open with body scroll lockedbfcache.js that re-syncs customer section data on every restore and reloads restored private pages (Safari keeps them in bfcache despite no-store)Magento_Swatches/templates/product/listing/renderer.phtmlMagento_Review/templates/form.phtml)overflow: hidden body lock is ignored, by freezing the body at its scroll offset while locked (Magento_Theme/templates/page/js/body-locker-init.phtml, web/tailwind/theme/layout.css)preventScroll (web/tailwind/js/bundle/menu.js)Magento_Theme/templates/html/header/topmenu.phtml)Warning Before upgrading Venta Theme on your own, read Updating to Venta Theme 1.7.1.
product_list_toolbar_preferences localStorage entry on toolbar change in Magento_Catalog/templates/product/list/js/init-toolbar-js.phtmlMagento_Catalog/templates/product/list/js/toolbar-preferences-js.phtml in <head>; explicit product_list_order/product_list_limit URL parameters take precedence, and categories with the “Static block only” display mode are skippedwindow.localStorage, matching the storage the pre-paint restore scripts readweb/playwright/tests/gallery-*.spec.ts)cms_image_hero, cms_image_banner, cms_image_tile and cms_image_inline image roles (with _mobile variants) for the CMS responsive image feature (etc/view.xml)Magento_Theme/templates/html/footer.phtml)cartHeartIconClass and cartHeartFilledClass getters for the cart button’s scoped hover group (Magento_Catalog/templates/product/list/js/wishlist.phtml)Magento_Catalog/templates/product/list/toolbar/viewmode.phtml and Magento_Catalog/templates/product/list/js/init-toolbar-js.phtmlproduct_list_toolbar_preferences localStorage entry and restored before first paint by Magento_Catalog::product/list/js/view-mode-restore.phtml, rendered inside the products wrapper on the category and search product listsmode-list Tailwind variant in web/tailwind/base/custom-variants.css, active under the wrapper’s products-list class, with the overrides inline as mode-list: utilities in the card templates; web/tailwind/components/product.css keeps only the list price styling, scoped by products-grid-card, and matches the legacy list card layoutmode-list:contents, in Magento_Catalog/templates/product/list/item-grid.phtml; the regions render only when the product list passes the show_description flag (mode switchable or list default), so widgets, carousels and grid-only stores keep the lean grid cardMagento_Catalog/templates/product/list/quantity.phtml, item-grid.phtml and the wishlist qty lookup in js/wishlist.phtmlMagento_Catalog/templates/product/list/js/product-card-actions.phtml; js/compare.phtml gains an onPrivateContentLoaded handleris_list_mode flag, always renders all options (kept in the DOM under the grid visibility classes) and one legend, revealed in list mode via mode-list: utilities, in Magento_Swatches/templates/product/listing/renderer.phtml and Magento_Swatches/templates/product/swatch-item.phtmlMagento_Catalog/templates/product/list.phtml always renders the grid card, so every List Mode configuration gets the list layout and the legacy Magento_Catalog::product/list/item-list.phtml card is retained but no longer renderedproducts-mode-switchable wrapper class, so stores configured with a single view mode keep their configured layout, in Magento_Catalog/templates/product/list/toolbar/viewmode.phtml, .../js/init-toolbar-js.phtml and .../js/view-mode-restore.phtmlSwitch_from_grid_to_list_view Playwright test now asserts the wrapper class toggle and unchanged URL instead of the product_list_mode URL parameter, in web/playwright/tests/poms/frontend/category.page.tssizes (Magento_Catalog/templates/product/view/gallery.phtml)<picture>, thumb-rail and fullscreen-dialog partials (Magento_Catalog/templates/product/view/gallery/)etc/view.xml)Hyva_Checkout/templates/default/checkout/address-view/address-list/grid.phtml)Magento_Wishlist/templates/php-cart/item/renderer/actions/move_to_wishlist.phtml, Magento_Wishlist/templates/shared-add-to-button.phtml)recaptcha_legal_notice block (Magento_ReCaptchaFrontendUi/layout/default.xml)web/tailwind/theme/checkbox.cssinitTierPricesInCatalog is now a page-wide component taking the product config as argument, in Magento_Catalog/templates/product/list/price/tier_prices.phtml and js/product-card-actions.phtmlMagento_Catalog/templates/product/view/gallery.phtml)Magento_Catalog/templates/product/view/gallery/picture.phtml)Magento_Catalog/templates/product/view/gallery/fullscreen-dialog.phtml)lg breakpoint (Magento_Catalog/templates/product/view/gallery/thumbs.phtml)Hyva_Checkout/templates/default/form/field/html/tooltip.phtml)Magento_Wishlist/templates/item/column/cart.phtmloverflow: hidden body lock (web/tailwind/components/ui.css)category_logo image entry to the Magebit_VentaTheme block in venta/etc/view.xml that was dropped in MHP-922lg — the button’s top-0.5 left-0.5 offsets are now desktop-only (Magento_Customer/templates/header/customer-menu.phtml).btn buttons showing the default cursor instead of a pointer on hover site-wide (web/tailwind/base/fallback.css)Magento_Sales/templates/order/info/buttons.phtml)Magento_Sales/templates/order/info/buttons.phtml)lg and 48px from lg (Hyva_Checkout/templates/default/section/terms/terms-wrapper.phtml)lg and 24px from lg (web/tailwind/theme/checkout.css)lg and 24px from lg (Hyva_Checkout/templates/default/navigation.phtml)Warning Before upgrading Venta Theme on your own, read Updating to Venta Theme 1.7.0.1.
generate-browser-jit npm script in web/tailwind producing tailwind.browser-jit.css for the in-browser Tailwind v4 CMS compilerhyva-themes/magento2-cms-tailwind-jit requirement to ^2.0 in composer.json, with suggest entries for the server-side bridge and recompile packagesetc/cms-tailwind-jit-theme-config.json pointing to a non-existent browser JIT config--radius-badge token (Magento_Theme/templates/html/header.phtml, web/tailwind/theme.css)Magento_Contact/templates/form.phtml, i18n/en_US.csv, i18n/lv_LV.csv)Warning Before upgrading Venta Theme on your own, read Updating to Venta Theme 1.7.0.
product.info.tabs layout block on the Product page (Magento_Catalog/layout/catalog_product_view.xml)Magento_Catalog/templates/product/view/tabs/tab.phtml)web/playwright/tests/product.spec.ts)product.info.additional on the Product pageview.xml image definitions for the image grid, image/text, team member and quote widgets (etc/view.xml)Magento_Catalog/templates/product/view/breadcrumbs.phtmlinitConfigurableSwatchOptions PLP listing component in the bundle - responsive-media image swap, attribute limits with a +N overflow chip, and the listing-configurable-selection-changed event that drives back-in-stock (web/tailwind/js/bundle/swatch-options.js)Magento_Swatches/templates/product/swatch-item.phtml)data-oos (and disabled without back-in-stock) in the initial HTML; client bindings update it per selection (Magento_Swatches/templates/product/swatch-item.phtml, web/tailwind/js/bundle/configurable-options.js)reflectOption, optionIsDisabled, getOptionLabel, selectedOptions and applyCheckedState members for the PHP-rendered configurable options (web/tailwind/js/bundle/configurable-options.js)select[name^=super_attribute] elements (web/tailwind/js/bundle/configurable-options.js)swatch_thumb image size 90×90 (etc/view.xml)Magento_Swatches view.xml tooltip_enabled = 1 (Magento_Swatches/templates/product/tooltip.phtml, product.swatch.tooltip blocks in the two swatch layouts, gated hooks in swatch-item.phtml / view/renderer.phtml / listing/renderer.phtml, tooltip members in web/tailwind/js/bundle/swatch-options.js)Magento_Catalog view.xml gallery/nav = end, start or center (Magento_Catalog/templates/product/view/gallery.phtml)product_swatch_image_large/_medium/_small image roles and the base Magento media image roles trimmed from the theme (etc/view.xml)gallery/loop, gallery/caption and gallery/nav view.xml toggles; all off by default, including when a child theme’s view.xml omits them (etc/view.xml, Magento_Catalog/templates/product/view/gallery.phtml)product-info.phtml into product/view/tabs/attribute-tabs.phtmlinitProductTab Alpine componentproduct.info.extrahint container to directly below the price on the Product pageimage_widget_mobile resize dimensions to 310x162 in view.xmlhyva-themes/magento2-default-theme from 1.4.6 to 1.5.2 and pinned hyva-themes/magento2-theme-module to 1.5.2 in the monorepo and in the theme package requirements (composer.json, app/design/frontend/Magebit/venta/composer.json)::backdrops use the new --color-backdrop token via bg-backdrop/backdrop:bg-backdrop (web/tailwind/theme.css, web/tailwind/components/ui.css, Hyva_Theme/templates/modal/modal-container.phtml, Hyva_Checkout dialog templates, Magento_Theme/templates/page/js/plugins/ajax-cart.phtml).backdrop uses min-h-svh instead of h-svh so inset-0 stretches fixed overlays to the full dynamic viewport (web/tailwind/components/ui.css)Magento_Swatches/templates/product/swatch-item.phtml, view/renderer.phtml, web/tailwind/components/swatches.css).swatch-option radio model, present in the initial HTML; grid cards keep the compact card styling while list rows render PDP-style swatches (48px, 44px on mobile) with attribute labels and the full option set, keyed into the block cache per display mode (Magento_Swatches/templates/product/listing/renderer.phtml, Magento_Swatches/templates/product/swatch-item.phtml, Magento_Catalog/templates/product/list/item-list.phtml, Magento_Swatches/layout/catalog_list_item.xml)+N overflow indicator render as plain text, image tiles are filled edge-to-edge, PDP text options are 48px (Magento_Swatches/templates/product/swatch-item.phtml, web/tailwind/components/swatches.css)web/tailwind/js/bundle/swatch-options.js); phtml JS templates emit config onlydata-force-pager, the track scrollbar is hidden on always-visible-scrollbar platforms, and fullscreen thumbnails are 106x122 on desktop / 60x70 on mobile (Magento_Catalog/templates/product/view/gallery.phtml, web/tailwind/js/bundle/snap-slider.js, web/tailwind/components/ui.css, web/tailwind/theme.css)window.SnapSlider for the vendor PageBuilder DOM widgets (web/tailwind/js/bundle/snap-slider.js, web/tailwind/components/content.css)gallery_switch_strategy to append and gallery loop/caption to 0 (etc/view.xml)@hyva-themes/hyva-modules to 1.4 (web/tailwind/package.json)<legend>, added autocomplete on telephone and comment fields, and the telephone input uses type="tel" (Magento_Contact/templates/form.phtml)enctype="multipart/form-data" only when a file-type custom option exists (Magento_Catalog/templates/product/view/product-form.phtml)Magento_Catalog/templates/product/list/js/wishlist.phtml)@setup data spec repairs coupon rules and restores salable stock (web/playwright)x-bind="overlay" / x-bind="popupContainer"); it keeps working through a compatibility layer that will be removed once all Venta extensions migrate to the native dialog markup (web/tailwind/js/bundle/modal-legacy-compat.js)Magento_Catalog/templates/product/view/product-info.phtmlhyva.modal overlay implementation (web/tailwind/js/bundle/modal.js); all modals use the theme-module 1.5.1 native dialog system (Hyva_Theme/templates/modal/*, page/js/modal.phtml, Hyva_Checkout magewire/evaluation dialogs)Magento_Catalog/templates/product/view/gallery-slider-image.phtml and its layout block (thumbnails render inline in the gallery pager)Magento_Swatches/templates/product/js/swatch-options.phtml (logic moved to the bundle)Magento_Swatches/templates/product/list/swatch-item.phtml, swatch-item-list.phtml, swatch-item-grid.phtml, product/js/init-configurable-swatch-options.phtml, Magento_Swatches/layout/hyva_catalog_category_view.xml)columns.top widget content on Category pagesproduct.info.additional.actionsMagento_Theme/templates/html/breadcrumbs.phtml and Magento_Catalog/templates/product/view/breadcrumbs.phtmlMagento_Catalog/templates/product/view/breadcrumbs.phtmlMagento_Catalog/templates/product/view/breadcrumbs.phtmlHyva_Checkout/templates/default/checkout/address-view/address-list/grid.phtml and Hyva_Checkout/templates/default/page/js/api/v1/alpinejs/address-view/address-list.phtmlHyva_Checkout/templates/default/page/js/api/v1/alpinejs/shipping/method-activate.phtml?color=&size=) render the checked swatches, selected labels and out-of-stock notify state server-side, removing the hydration layout shift (Magento_Swatches/templates/product/view/renderer.phtml, Magento_Swatches/templates/product/swatch-item.phtml, Magento_Catalog/templates/product/view/addtocart.phtml, product-info.phtml, addtocompare.phtml, addtowishlist.phtml)Magento_Customer/templates/form/login.phtml, register.phtml, forgotpassword.phtml, edit.phtml)Magento_AdvancedSearch/templates/search_data.phtml)x-data/@click/:class expressions replaced with the registered attributeAccordion component (Magento_Catalog/templates/product/view/product-info.phtml)private-content-loaded dispatch; it now seeds from the persisted section data with the dispatcher’s version and expiry validation (Magento_Customer/templates/header/customer-menu.phtml)UTF-8 argument on mb_strtolower in the checkout order comment templatehyva-themes/magento2-hyva-checkout from 1.3.10 to 1.3.12 in root and theme composer.jsonWarning Before upgrading Venta Theme on your own, read Updating to Venta Theme 1.6.4.
Magento_Checkout/templates/php-cart/item/default.phtml, Magento_Sales/templates/order/items/renderer/default.phtml, Magento_Checkout/templates/success/order/items/renderer/default.phtml, Magento_Wishlist/templates/shared.phtml, Magento_Review/templates/customer/list.phtml)customer_review_list_thumbnail_mobile image role (80×80) for the My Reviews list (etc/view.xml)Hyva_Checkout/templates/default/page/footer/agreement-links.phtmlventaCheckoutFooterAgreements Alpine component in Hyva_Checkout/templates/default/page/js/api/v1/alpinejs/footer-agreements.phtmlbanner_widget_big_tablet/_mobile, banner_widget_small_top_tablet/_mobile, banner_widget_small_bottom_tablet/_mobile) under a Magebit_VentaTheme module block in etc/view.xmlcategory_logo_mobile 52x52 image size in etc/view.xmlmagebit/menu/slice as memoized depth-two slices (Magento_Theme/templates/html/header/topmenu.phtml)header.menu.desktop.widgets, header.menu.dropdown.widgets, header.menu.mobile.widgets) in Magento_Theme/layout/default.xmli18n/en_US.csv, i18n/lv_LV.csv, i18n/nl_NL.csv)<link rel="preload" as="image" imagesrcset> in <head><picture> (WebP/retina) in grid, list, wishlist and compare (Magento_Catalog/templates/product/list/image.phtml)max-width:100%;height:auto (Magento_Catalog/templates/product/list/image.phtml, etc/view.xml)Magento_Catalog/templates/product/slider/product-slider.phtml, linked/vertical/container.phtml, etc/view.xml)etc/view.xml (<vars> breakpoints + image roles) and read via the Breakpoint view model, so a child theme overrides them from its own view.xml (ViewModel/Breakpoint.php, ViewModel/Product/CardImageBreakpoints.php)<picture> matching the main image’s sources (Magento_Catalog/templates/product/list/image.phtml)Magento_Swatches/templates/product/js/init-configurable-swatch-options.phtml)etc/view.xml)view/frontend/templates/widget/product_list_widget.phtml)<script> blocks with registerInlineScript() nonce calls across the cart page templates in Magento_Checkout/templates/php-cart/ (coupon.phtml, shipping.phtml, totals.phtml, form.phtml)x-data, object-literal/ternary/logical bindings, method-call x-for, literal-argument event handlers, :selected comparisons, x-model) as registered Alpine.data components on the cart page, using getter properties (incl. precomputed x-for arrays) and no-paren method references (required by the Alpine CSP build)<script> blocks with registerInlineScript() nonce calls across the Customer & Account templates in Magento_Customer/templates/ (incl. account/authentication-popup.phtml, form/register/agreements.phtml, account/link/authorization.phtml)x-data, ternaries, event-handler mutations, literal-argument handlers, x-model) as registered Alpine.data components across the same Customer & Account templates, using getter properties for bindings and no-paren method references for event handlers (required by the Alpine CSP build)Magento_Theme/templates/mini-cart/slider/js/slider-init.phtml, mini-cart/slider/recently-viewed/recently-renderer.phtml)Magento_Theme/templates/page/js/plugins/ajax-cart.phtml, js/toolbar/init-pager-js.phtml)Magento_Wishlist/templates/view.phtml, sharing.phtml, sortable-item/link.phtml)Magento_AdvancedSearch/templates/search_data.phtml)Magento_Theme/templates/html/header.phtml, header/top-header.phtml, header/menu/hamburger.phtml, header/topmenu.phtml)html/switcher/form.phtml, page/js/store-switcher-init.phtml)Magento_Contact/templates/form.phtml)Magento_Review/templates/form.phtml, helper/summary.phtml)Magento_LoginAsCustomerAssistance/templates/shopping-assistance.phtml)Magento_NegotiableQuote/templates/checkout/cart/link.phtml)Enable Custom Footer Links setting in Hyva_Checkout/layout/hyva_checkout_venta.xmlHyva_Checkout/templates/default/page/footer.phtml to render custom links and agreement popup links in a single rowbanner_widget_big/banner_widget_small_top/banner_widget_small_bottom image sizes in etc/view.xml into the Magebit_VentaTheme module blockMagento_Catalog/templates/category/subcategory-tile.phtml) to render a mobile-specific image up to 1023px via getResponsivePicture mobileMaxWidthMagebit_ImageResizer image sizes (category_logo/_mobile, image_widget/_mobile, banner_menu/_mobile, category_block_list_widget/_mobile, brands_widget, block_widget_logo) into the Magebit_VentaTheme block in etc/view.xml and removed the now-empty Magebit_ImageResizer block (dropping the duplicate order_view_thumbnail_image already defined under Magento_Catalog)Magebit_VentaTheme module to the category_logo resizer calls in Magento_Catalog/templates/category/subcategory-tile.phtml and the banner_menu/banner_menu_mobile calls in Magento_Theme/templates/html/header/topmenu.phtmlchildren_count); magebit_theme/header/menu_depth (default 7) caps drill depthjs/bundle/header.js, js/bundle/menu.js) as CSP-safe Alpine.data, with ventaBundleConfig bridges for translated stringsinitPanelAutoClose in topmenu.phtmlscrollTop store and the product-compare count into a compareCount storearia-* variants + nav-current) and removed all !important from the menutext-link colour tokens and replaced per-item border-* with divide-y/divide-x on parentsheader/wrapper.phtml and switcher.phtml to registered CSP-safe Alpine.dataheader.phtml sticky-header scroll engine inside an IIFESvgIcons::renderHtml instead of the magic methods.table-orders tables with CSS grid lists on Dashboard Recent Orders, My Orders, and Address BookMagento_Checkout/templates/php-cartweb/tailwind/theme.css for orders, address, stock alerts, cart lists, and mobile card labelsMagento_Sales/templates/order/list/items.phtml and row.phtmlMagento_Theme/templates/html/pager.phtml to always show the “Items %1-%2 of %3” count formatHyva_Checkout/templates/default/express-payments.phtml)Hyva_Theme/templates/page/js/confirm-js.phtml)Magento_Catalog/templates/product/image.phtmlx-defer="intersect" from header/menu/hamburger.phtmlheader-backdrop render and unused isLoading state from header.phtml.table-orders, #my-address-table, and #my-orders-table styles from web/tailwind/components/content.css:open pseudo-class across all form-select elementsSvgIcons view modelHyva_Checkout/templates/default/express-payments.phtml on the entry step instead of a hard-coded step positionaction.phtml using isSaleable()overflow-x-hidden on the list)openPreviousCategory on empty panel history (topmenu.phtml)wrap-break-wordh-9/lg:h-10 height instead of max-h-9/max-h-maxhyva.replaceDomElement (Hyva_Theme/templates/page/js/hyva.phtml, both activateScripts and removeScripts) now preserves inert <script type="application/json"> config islands instead of relocating/stripping them<link rel="preload"> for css/styles.css in default_head_blocks.xml merging with Hyvä’s <css src="css/styles.css"/> into a single malformed tag with duplicate rel/type attributesmagebitcom/magento2-venta-theme-module to 1.6.3.1Have questions we didn't answer?Get In Touch
OnlineVenta isn’t just a service; it’s a solution to the problems our clients trust us to resolve. We understand that every business is unique, so we're flexible in our approach. Tell us your dreams, and we'll make them a reality.
We use cookies.
Some help us see how the site is used and measure our ads. You choose — until you do, no cookies are set and Google receives only cookieless signals that don't identify you.
