Jump to >

Power Pack 1.4.3 Release Notes

Release date: March 29, 2017

New Features

  • Added support for Git repositories hosted on Visual Studio Team Services.

    Power Pack 1.4.2 added support for TFS repositories hosted on Visual Studio Team Services, and we now support Git repositories as well.

  • Added compatibility with Review Board 3.0.

Bug Fixes

PDF Document Review

  • Fixed some rare CORS issues when running with DEBUG=True.

    If DEBUG was turned on for the server and static media is hosted on a separate domain, some browsers would fail to load important JavaScript used in the PDF renderer due to a Cross Resource Origin Sharing (CORS) violation. This has been fixed.

  • Fixed display of comment images in e-mails.

    When static media is served from the same domain as the Review Board application, the images for comments made on PDF documents (the selected regions) were being included in HTML e-mails with only relative URLs, which naturally could not be found. These are now referenced using absolute URLs including the server name.

Team Foundation Server

  • Fixed a bug where the post-commit review request UI was adding an additional / in diff file paths.

    This bug, which would cause some post-commit review requests on TFS to fail, was caused by an incompatibility between some versions of Review Board and Power Pack.

  • Improved error messages when TFS credentials have changed.

    If the password for a TFS repository had changed, Review Board would show an incomprehensible error and did not allow changing the stored password. This has been fixed up.

  • Fixed .snp files being mistakenly reported as binary.

    Files ending in the .snp extension were reported by the TFS server as being application/msaccess regardless of their content, and were therefore being ignored as binary. These are now treated as text if they contain text content.

User Management

  • Fixed manual removal and added auto-removal of deleted users from licenses.

    If a user was added to a license and that user was then deleted from the database, the licensed user entry would still remain, taking up a seat. Deleting that licensed user entry would lead to a crash, with the entry remaining in the database.