Getting help

Stuck? Have a look into the documentation.
You can also get support by joining our mailing list.


I have bought a commercial license, now what?
Once we can verify the payment you will receive an email including the license and support contact. In the meanwhile, of course, you can start becoming familiar with ReportBro.
Why can't I see images and buttons in ReportBro Designer in Firefox?
ReportBro uses icon fonts instead of images and due to Firefox's strict origin policy they cannot be loaded when running a demo on your local machine (from ../dist/iconfonts). In your Firefox browser go to about:config and make sure security.fileuri.strict_origin_policy is set to false.
Why is there no PDF preview in Microsoft Edge?
In case of using a report server on localhost you have to enable loopback first with CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe
see also
What if my server application is not written in Python? Can I still use ReportBro?

The best solution is to create an own application which is only responsible for generating reports. This application could be similar to the demo application but without any templates and views to view and edit the data. The app should connect to the same database as your main application so it can directly query all necessary data for the reports.

Run the python application on a different port (e.g. 8100) and every time you show a report you just link to this application (e.g. http://localhost:8100/albums/album/report to get the albums report in the demo app). Alternatively you can also use a web request to get the report in case you need it server-side (e.g. to store the pdf in the db or to merge multiple pdfs).

If the reports can only be accessed with authentication you either have to implement authentication on the report server as well or you do not allow direct access of the reports from outside and instead only allow access from your main application (where you can fetch them with a web request).

How can I add additional fonts?

Additional fonts must be added in ReportBro Designer and in ReportBro Lib. To set additional fonts in the Designer you must specify the additionalFonts property when initializing the reportBro instance. See ReportBro Designer Options for a description of the property. An example code can be seen in the Certificate Demo - the initialization code is shown on the overview Demo page.

On the server the same font must be added as additional_fonts parameter when creating the reportBro.Report instance. See ReportBro Lib Arguments for a description of the parameter.

Below is an example code to add the Lobster TrueType Font (only showing the relevant parts to add a font):

Client code:
<style type="text/css">
        @font-face {
            font-family: "lobster";
            src: url("fonts/lobster.ttf");
    $(document).ready(function() {
            additionalFonts: [ { name: 'Lobster', value: 'lobster' } ]
Server code (Django app):

    from import staticfiles_storage
    additional_fonts = [
        dict(value='lobster', filename=staticfiles_storage.path('lobster.ttf'))
    report = Report(json.loads(report_definition.report_definition), params, additional_fonts=additional_fonts)

It is important that the font is available client-side and on the server. Further the font value ('lobster' in our example) must be exactly the same in the font-face css definition, in the value of additionalFonts in the Designer initialization and in the value of additional_fonts array passed to the ReportBro Lib instance.

Does ReportBro support Chinese?

Yes, you need to use a font which supports all your characters you want to print. The standard fonts do not include Chinese characters.

See question above how you can include additional fonts. Make sure the text elements in ReportBro Designer which displays Chinese characters uses your additional font so the text can be printed.


The latest version of ReportBro is compatible with
  • Firefox 53+
  • Chrome 58+
  • Safari 9+
  • Internet Explorer 10, Microsoft Edge 14+
  • Opera 46+
To work as intended ReportBro requires

Requesting a feature

Came across an idea for a new feature? Please follow these steps:
  1. Check for an existing request
    Maybe someone else already submitted the same request - please check existing issues before adding a new request. You may upvote existing requests by reacting with a "like" on the issue. Make sure to also subscribe for notifications in order to get updates on the request.
  2. Describe the new feature
    Provide us with a use case, detailed description and your ideas for implementation of the feature.
  3. Use the issue tracker to submit the feature
    If you have fulfilled the above steps submit the feature request to the ReportBro Designer issue tracker or ReportBro Lib issue tracker on Github.

Reporting a bug

Found something in ReportBro's behavior that isn't quite right? Can you reproduce it? If your answer to both questions is 'yes' follow these steps:
  1. Describe your test case and test loop
    Provide details about what you wanted to do and how you did it in as much detail as possible. Tell us, on which platform (Windows, Mac, Linux), browser and browser version you discover the bug.
  2. Provide a reproducable test
    Submit your report's JSON in a text file. Make sure that it is runnable - test it by setting reportServerUrl to its default (see configuration options)
    We can only work on reproducable issues - using your report JSON and following your test loop must allow us to reproduce the bug using the default ReportBro server.
  3. Describe the bug
    Describe the intended versus the actual behavior. Screenshots are helpful too. The more details you can provide, the better.
  4. Use the issue tracker to submit the bug
    If you have fulfilled the above steps submit the bug to the ReportBro Designer issue tracker or ReportBro Lib issue tracker on Github.