Storefront known issues

This topic describes known issues in the Oracle Commerce storefront.

33602031 Updating a product's image links returns price information in the endpoint response

The updateProduct endpoint erroneously returns price information in the response when updating product image links.

28498173 Type ahead alignment missing for products with 12 digit prices

Products with prices requiring 12 digits to be displayed are not aligned.

Workaround: Enlarge the width of the widget level CSS. This is a styling issue which may be corrected by adding the below lines of CSS styles to the theme when using 12-digit prices.

additional-styles.css
.typeaheadProductName {
  .make-md-column(5);
  white-space: normal;
  padding-top: 5px;
  word-wrap: break-word;
}
.typeaheadProductPrice {
  .make-md-column(4);
  .pull-right;
  text-align: right;
  padding-left: 0px;
  padding-right: 17px;
  padding-top:5px;
  padding-bottom: 0px;
  white-space: normal;
}

22490198 Rich text dynamic property value is shown with arrow symbols

On the Search Results page, rich text property values are shown with arrow symbols, for example “↵↵Full sleeved shirt”.

21854293 Error notifications do not clear after resolving the errors on checkout and cart pages

On the store’s cart and checkout pages, several error messages remain visible after the errors have been resolved.

22911731 Using pagination controls on the product listing page displays 404 message

Style-based products which span several pages may display a 404 error message as their pagination controls fail.

Workaround: Turn off style based listing in the Product Listing widget.

30806845 Preview displays default collection instead of site-specific collection

When previewing your store, changing to a site other than the default one and updating the site language does not display site-specific collections for the site and language you have chosen. Instead, the default collection remains on display in the default language.

31353670 Updates to view models can create naming conflicts

A recent update to the Address view model added a new addressType property that could conflict with a custom property of the same name that some merchants may have previously added.

Workaround: If you add custom properties to a view model, you should begin the names of these properties with an underscore or some other prefix. Doing this ensures that naming conflicts do not occur if Oracle adds new properties to the view model. For example, if you had added a property named _addressType, it would not conflict with the new addressType property.