If you’re already a Hitchhiker, log in to access this content.
Debugging the Frontend| Hitchhikers Platform
What You’ll Learn
In this section, you will learn:
- What a frontend issue is
- Common issues and how to troubleshoot
When you notice display issues on an Answers page, you’ll want to debug the frontend. You can begin debugging the frontend once you’ve published a build to Staging or used the Live Preview functionality. It’s possible that your recent build or preview has produced some funky results on the frontend, like the below:
If we see something like this, we automatically know that there is a frontend issue. The FAQ vertical is not structured as an accordion CardType, which we know is always the case with FAQ cards. The Vertical is also missing a “FAQs” section title. These are two signals that something is off in your frontend.
Here’s another example where we see the Menu Items vertical tab missing in the front screenshot, and there is no Vertical section title for “Menu Items” here either. This is another signal to check the frontend files, where you configure your Verticals and data mappings for the experience.
In this example, the blank page produced a console error. You can usually determine the issue type within the console error itself. In this example, the error reads: “MapProviderKey” is not defined. Therefore, an Administrator can infer that there is an issue with the Maps API Key and troubleshoot from there.