Frequently Asked Questions

Which browsers does BugMuncher support

BugMuncher has been built to work in many different browser / operating system combinations. In fact it’s easier just to list what isn’t supported.

BugMuncher does not support the following:

  • Internet Explorer 7 and older
  • Users who have JavaScript disabled
  • Lynx and other text browsers

Can BugMuncher be used over SSL (https)?

Yes it can! By default BugMuncher will load over the SSL if your site is loaded over SSL. You can also choose to always or never load BugMuncher over SSL, although I wouldn’t recommend choosing to never load BugMuncher over SSL, unless you have a very good reason for doing so.


Will BugMuncher work on areas of a site where users need to be logged in?

Yes BugMuncher will work fine on pages and websites where the user needs to log in for access.

The only time when it may not work properly is if your site uses HTTP basic access authentication which also restricts access to images and CSS files. Please see the next question to see how to overcome this problem.


I've installed BugMuncher but the screenshots aren't correct

This happens because the BugMuncher server needs to be able to access your website’s assets (CSS, images, fonts, etc) in order to create the screenshot. There are two common scenarios which can stop BugMuncher being able to reach your asset files:

Testing BugMuncher on a local server:

Unfortunately you cannot test BugMuncher on your local environment, as there is no way for the BugMuncher server to access images and CSS files on your local machine. Instead try testing BugMuncher on your online testing or staging server.

Using BugMuncher on a server which is behind HTTP basic access authentication:

While BugMuncher will work on sites that are behind authentication, HTTP basic access authentication is often set up as a blanket restriction for the whole site, restricting access to everything including images and CSS, instead of just restricting access to pages.

You can give BugMuncher access credentials in order to access content behind basic authentication by adding an http_auth property in your bugmuncher_options object, eg: if you wanted BugMuncher to use the username ‘BugMuncher’ and password ‘Pa55word’

var bugmuncher_options = {
    http_auth:'BugMuncher:Pa55word',
    api_key:'YOUR API KEY HERE'
};

Missing or incorrect webfonts

Some browsers will not load webfonts from domains other than that of the host page. This means if your site uses self hosted webfonts, those fonts may not be displayed in screenshots. To fix this you need to allow Cross Origin Resource Sharing (CORS) on your webfonts:

Nginx

location ~* \.(eot|ttf|woff|woff2|otf)$ {
  add_header Access-Control-Allow-Origin '*';
}

Apache

<FilesMatch ".(eot|ttf|woff|woff2|otf)">
  Header set Access-Control-Allow-Origin "*"
</FilesMatch>

If you’re still having problems getting BugMuncher working correctly please get in touch.


Can I just use BugMuncher for internal bug tracking before releases?

You can absolutely just use BugMuncher internally, how you achieve this depends on your setup. Eg: If you have an internal testing site you can just add the BugMuncher embed code to that site. However if you want BugMuncher on your live site but only shown to you team members you’ll need some kind of conditional logic that would only include the BugMuncher embed code for specific users.

If you need any help setting this up, please get in touch.


If I eat myself, will I become twice as big, or disappear?

Well of course you would, er, hang on a second…


My question isn't here

Email your question to info@bugmuncher.com or use the contact form - you’ll get a quick reply AND your question will be listed on this page, what more could you ask for?