Troubleshooting Your Implementation

If you are experiencing an issue in UCP and are using a custom theme in your implementation, Kibo Support recommends that you set up a tenant with the default "Core" theme for debugging purposes. Creating this version of your production site allows you to identify whether the problem is in the Core platform or your theme customization, which can help narrow down the underlying cause and solution.

  1. In Admin, go to System > Settings > Sites. Create a new site with exactly the same Catalog, Currency, and Locale as the site you are testing under core. For example, if you have a single site named “Mystic Sports”, create a new site named “Mystic Sports Core” with the same settings. Wait 10 minutes for the site to fully provision.
  2. Go to System > Settings > General and make sure all the of settings match the Core site. Upload a Robots.txt file as shown below to make sure search engines don’t crawl the Core site. Technically this may be unnecessary as sites without primary domains will send a “x-robots-tag: noindex, nofollow” header, but it is still good practice to include.
    User-agent: *
    Disallow: *
  3. Go to System > Settings > Payment Types. Make sure the payment types are configured the same way as the main site, but do not use any NoOp payments.
  4. Go to Customization > Custom Routes and copy over the same custom route configuration (including any API Extension routes) into the new site.
  5. Go to Main > Site Editor > Themes. Make sure that “MozuCore” is selected as the theme for the Core site.
  6. Add the Core site to your location groups, if your tenant is not eCommerce-only. You must have Order Management enabled in order to configure location groups.
  7. Configure order routing for the Core site, if your tenant is not eCommerce-only. You must have Order Management enabled in order to configure order routing.
  8. Recreate any discounts for the Core site, because discounts are managed at the site level.
  9. In Settings > Shipping, copy over all shipping methods that are visible on the storefront and set the default “ship from” location.
  10. Make sure that any custom applications in System > Customization > Applications that need site level settings are configured for the new Core site.

Now, you should have a site that runs on the standard Core theme without any customization. Now you can attempt to reproduce the issue you were experiencing on your production site and provide more information about the problem to Kibo Support as needed.


Note: API Extensions

API Extensions (formerly known as Arc.js) are enabled for both sites, so this can lead to an error still occurring on the Core Theme even if the root cause is in customization via API Extension actions. However, you can configure API Extensions to only apply to certain sites for troubleshooting purposes if needed.

Was this page helpful?