Testing your Frontend / Debugging

This page suggest the tests to perform when setting your Styla Frontend up and before you go live with it. It also lists possible causes for problems.

Check your Frontend visually

  • if the content looks as you expect it to look like

  • if all the elements rendered as expected on desktop, tablet, mobile view ports

Possible solutions:

  • update your page content with the Editor

  • update your bases with the Editor

  • update your CSS with the Admin

  • update your custom modules

Check if all pages available

  • if pages you publish with the Editor available on the domain you have pointed at Styla Frontend

  • if product details and category pages available

Possible solutions:

  • check if your domain settings correct

  • check if your bases set up correctly

  • check if BigCommerce API credentials correct and set up correctly in the DOMAIN CONFIGURATION JSON

Check if re-rendering triggered as expected

  • publish an updated version of a page in the Editor

  • update a product description in your BigCommerce

  • update your base and click the “Save and Re-render“ button top-right

Possible solutions:

  • check if your bases set up correctly

  • check if BigCommerce API credentials correct and set up correctly in the DOMAIN CONFIGURATION JSON

  • pass the bug report to your Onboarding Manager

Check if shopping flow working as expected

  • if newly created user accounts show up in BigCommerce

  • if login works

  • if password reset works

  • if prices and product details o Styla Frontend in line with BigCommerce

  • if products can be added to the cart

  • if checkout works and orders show up in BigCommerce

Check if search working as expected

  • if search results show up as expected for products, categories, content pages, both in the search input and on the search results page

  • if content updates for products, categories, content pages are reflected both in the search input and on the search results page

Check if your custom modules working as expected

  • the functionalities and testing flow depend on a specific module

  • but check if data saved in your module is visible in its JSON (by adding /json to the module’s URL in the Editor)

  • also, if any content delivered by handlebars is prerendered, so shows up in your browser even with JavaScript switched off