Funnelback 16.10 patches
Patches
Type | Release version | Description |
---|---|---|
3 Bug fixes |
16.10.0.10 |
Removed unused Honeycomb tooling that consumes resources and fills up a log file with noise. |
3 Bug fixes |
16.10.0.9 |
Fixed the issue where the Perl script to trigger analytics update didn’t set the correct update type. |
3 Bug fixes |
16.10.0.8 |
Fixed an issue where the environment was not detected correctly in the configuration, resulting in configuration key values to revert to the default value. |
3 Bug fixes |
16.10.0.8 |
Fixed an issue with client-based APIs where incorrect permissions were returned. |
3 Bug fixes |
16.10.0.8 |
Fixed an issue with the Added a new option The extraction of relative links now follows the W3C standard regarding the validity of HTML pages. |
3 Bug fixes |
16.10.0.7 |
Fixed an issue that prevented internal documentation within the administration dashboard from displaying in some circumstances. |
3 Bug fixes |
16.10.0.6 |
Fixed an issue that caused administration dashboard labels to display intermittently. |
3 Bug fixes |
16.10.0.5 |
Fixed an issue where the Freemarker template upgrader incorrectly upgraded custom variables named |
3 Bug fixes |
16.10.0.5 |
Fixed an issue where trend alerts notifications were not generated. |
3 Bug fixes |
16.10.0.5 |
Fixed an issue preventing the correct export of content auditor and accessibility auditor documents in CSV format. |
3 Bug fixes |
16.10.0.4 |
Fixed an issue where adding a new category to a tab or custom facet via administration UI was prevented in some conditions. |
3 Bug fixes |
16.10.0.3 |
Fixed an issue where an invalid profile value provided in the search request returned a 500 server error. |
3 Bug fixes |
16.10.0.3 |
Fixed an issue where unknown product configuration key values are not expanded correctly for the |
3 Bug fixes |
16.10.0.2 |
Fixed an issue where fetching Facebook comments would cause an infinite loop due to changes within the Facebook endpoints. |
3 Bug fixes |
16.10.0.1 |
Fixed a security vulnerability where com.google.oauth-client hasn’t implemented PKCE support in accordance with the RFC for OAuth 2.0 for Native Apps. |