v4.5.15.16 release

v4.5.15.16 had three bug fixes.

Significant defects addressed

• Corrected an issue preventing correct selection of a content form when that content form is associated with a user itself associated with a site-specific role. For example, the content edit form Recipe is derived from Article and associated with the role Editor. Adam Braun is an Editor. In this scenario, when Adam Braun started a new asset based on Article, the default Article content edit form appeared instead of Recipe.
• Restored the For Developers tab in an asset's Tools widget for users with the default Full Access role. See "Breaking changes," below.
• Corrected vulnerabilities detected by the OWASP dependency checker.

Breaking changes

• Projects may not not want to expose the Developer tab in an asset's Tools widget for the default role. In such cases, update missingRolePermissions to include -developer/info (or -developer/ to exclude all developer features from the default role).