Cloud UI 1.2 introduces a initial separate UI that can be used for most product detail pages, extending building on the 1.0 release, which enabled a separate UI for the Pricing Calendar . Cloud UI is our standalone application layer that decouples frontend code from the nopCommerce backend. Separating the UI from the API infrastructure provides the following benefits:
More frequent, lower-risk frontend-only releases
Creation of distinct, releasable units
Shift toward a modern application server framework
Improved page load performance over time as more of the site is migrated to this framework
The Cloud UI is the foundation for our upcoming redesign and moving toward additional redesigns of the shopping pages.
| Note |
|---|
IMPORTANT: While Cloud UI is supported for most product detail pages, there are some features and configuration options that are not yet supported in the Cloud UI, that . These configurations will continue to work as usual if loaded on legacy. In this guide we detail which the Legacy pages. |
This guide explains the following:
Which product detail pages should NOT be moved over to Cloud UI, and
...
how to ensure that these products continue to load and work on the
...
non-Cloud UI (see the list below)
Which products are now supported and will load in the
...
separate Cloud UI.
Detailed Setup Guide
Most products are Cloud UI compatible, but there are some exceptions. For these exception products, there is a new product-level setting that enables some products to continue to load for users in the legacy UI, and for the majority of products to load in the new Cloud UI. To flag a product so that it continues to load in the legacy ui, find the product from Catalog > Products >Edit.
A new product-level setting called “Use Legacy Product Page” has been added to the set of Aspenware Commerce settings that should only be turned on if a product is incompatible with the Cloud UI (details below).
...
Which products are incompatible with Cloud UI V1?
Initially, the user experience and UI will be identical between legacy and Cloud UI pages. With the upcoming PDP refresh release, the Cloud UI product detail pages will have a refreshed look and feel and theme application according to our design system, while legacy product detail pages will remain unchanged.
Which products are currently incompatible with the Cloud UI PDP?
Most products are Cloud UI compatible, but there are some exceptions. If a product has any of the following features/configurations enabled on the PDP it should NOT load on the Cloud UI and should be flagged to continue to display legacy PDP. These products will continue to work so long as they are not loaded on Cloud UI. if they retain their Legacy configuration and are flagged as noted below in the Setup Guide.
Radio button date products (section 2 of this guide) (expected to be Cloud UI compatible in 1.5)
Time-based activity products (expected to be Cloud UI compatible in 1.5)
Assigned to attribute enabling with Assignment on the PDP
Affirm enabled Fenced products Products that can only be accessed using a valid voucher
Reservation Affirm enabled products
Fast Flow
...
Detailed Setup Guide
For these listed exception products, there is a new product-level setting that enables some products to continue to load for users in the legacy UI, and for the majority of products to load in the new Cloud UI. Respecting this routing will work whether a PDP is accessed via the category page, related product link, or cross-sell link. To flag a product so that it continues to load in the legacy UI:
Find the product from Catalog > Products >Edit
Scroll to the Aspenware Commerce section of the edit page
Locate the new product-level setting called Use Legacy Product Page.
Check the box
Click SAVE ALL SETTINGS
| Info |
|---|
NOTE: This setting should ONLY be turned on if a product is incompatibale with Cloud UI. |
...