BugLogHQ 1.7 brings the following changes/features:

• A new "Dashboard" homepage.
• More granular and finer timespans to view received errors.
• A log of each time an alert is fired with information on the bug report that triggered the alert.
• Optional HTTP Basic authentication for access to RSS feeds.
• Expose the results of any search criteria as an RSS feed.
• A new client written in JavaScript to allow client-side webapps to report errors to a BugLog server.
• Centralized and standardized display of dates and times, including support for time zone conversion.
• Display additional insights and context for each bug report (timeline, other reports from same user agent, host distribution)
• Allow deletion of bug reports.
• Improved listing of current rules to provide a human-readable description of what they actually do.
• Use jQuery and Twitter Bootstrap for the main user interface.

Getting and Installing or Upgrading BugLogHQ

There are a couple of ways in which you can get the latest release from BugLogHQ. As usual you can get the latest stable release from RIAForge at http://bugloghq.riaforge.org/ or if you want to get a snapshot of the current trunk, you can get it from GitHub at https://github.com/oarevalo/BugLogHQ. Also, if you are using GIT and want to be able to get the latest changes, then another way to get BugLog is by cloning the repo: The default installation of BugLog is a fairly simple process:

1. Unpack (or clone) into a directory named bugLog right under your web root (so that you can access it at http://your_server/bugLog)
2. Create a datasource named buglog
3. Execute the SQL script for your database engine (found in /bugLog/install)

And that's it! For other installation options check out the README.MD file in the bugLog directory. Upgrading is even easier:

1. Make a copy of your main config file (/bugLog/config/bugLog-config.xml.cfm) and keep it somewhere safe
2. Replace your existing bugLog installation with the downloaded version
3. Restore your bugLog config file to the same location as before.
4. Check the /bugLog/install/migration directory to see if there is a SQL script for the version that you are upgrading to and execute it. Note that Not all version changes require database changes.
5. Go to http://your_server/bugLog/hq and click on the "reset app" link near the login prompt.

I hope you find the new additions to BugLogHQ to be useful to you, and please feel free to join the mailing list to report any bugs, ideas or problems you may encounter.