Sidebar not appearing!

Follow

A common issue with the BugHerd sidebar is that it's not showing on your site, but you do expect it to. Here are some steps to follow to help you check for the common problems.

Because the sidebar doesn't show up on your site at all when it's not supposed to, it is not immediately obvious for what reason. These are the possible causes:

Not logged in

The BugHerd sidebar only shows to authenticated users who have an account on www.bugherd.com. BugHerd uses a 3rd party cookie to remember your login so that the sidebar will show on your site for all the invited users. It's possible that cookies have been deleted, or that you are using a different browser or different computer from when you last logged into BugHerd. If you're using the browser extension you may need to close the browser and open it after logging in for the extension to detect that you're logged in.

Ad blocking extensions (adblock-plus, uBlock etc.)

Ad blocking extensions sometimes identify the BugHerd sidebar as an ad and prevent it from loading. You might need to disable your ad blocking extension or add an exception for BugHerd to your ad blocking extension to get the BugHerd sidebar to load.

Incorrect project key

If you have multiple projects, it's possible that the incorrect widget was installed on the site. So someone who is a collaborator on project A but project B's widget is loaded, then the sidebar won't show. Note that if you use Web Developer tools, the HTTP error code BugHerd for this issue is: 422. This error code indicates you are logged in, but you are not a member of the project.

Project not enabled

The project owner can disable certain projects. In this case the sidebar will no longer show. It's also possible that this happened because their plan expired. The HTTP error code used is 403. This indicated you are logged in and are a member of the project, but the project is disabled for all users.

Multiple projects using the same domain

Please be careful when specifying reused domains such when working on multiple projects. If you specify the same domain for different projects, BugHerd won't know which project's sidebar to show, and will not display the sidebar at all. The solution in that case is to embed the BugHerd javascript code manually. Then you always know you are logging bugs on the right project.

Being blocked by another extension

Sometimes ad-blocker or firewall type browser extensions can prevent BugHerd displaying, so if you have recently updated or install a extension like this, try disabling before trying again.

BugHerd is blocked at a network level

This usually only occasionally applies for government departments or large corporations, but it might be worth checking with your IT department to make sure that there aren't security settings in place that override your own personal terminal, as these security settings can often be set without your knowledge.

Summary of the HTTP error codes

200: either the sidebar content is returned (and should display), or the user is not logged in
403: project disabled
422: not a member of the project

Have more questions? Submit a request

Comments

Powered by Zendesk