Skip to content

v17.4.1 - tree permission bug

Choose a tag to compare

@Luuk1983 Luuk1983 released this 13 Oct 09:16

Warning

Breaking changes

  • Umbraco 17.4.0 or later is now required (previously 17.3.0). Update Umbraco before updating this package.
  • The /effective endpoint now requires access to the Users section. The backoffice no longer uses it to decide which content actions a user can perform; it now uses Umbraco's own permission endpoint, which goes through Advanced Permissions since Umbraco 17.4. This only affects you if your own code calls /umbraco/management/api/v1/advanced-permissions/effective for users without Users-section access.

This is a bug fix release.

Content tree empty for some user groups

A user group could be given Read on content in the Permissions Editor, while its users still saw an empty content tree. The Access Viewer did show Read as allowed on every node, so nothing looked wrong in the package itself.

The cause: since Umbraco 17.2, the content tree only shows nodes where the user has Read, and it checked Umbraco's own user group permissions for that, not Advanced Permissions. Advanced Permissions hides those Umbraco permissions in the user group editor, so a user group created after installing the package doesn't have Read there.

The reverse also happened: a node denied in the Permissions Editor could still show up in the tree, although opening it was correctly blocked.

Why most installs didn't notice: Umbraco's default user groups (Editors, Writers and so on) come with Read already set, and the package copies those permissions into Advanced Permissions when it's installed. For those groups, both sources said "Read allowed", so the tree looked right. It only went wrong for user groups created later, or where Read was denied in the Permissions Editor.

The tree, and the other places in the backoffice that ask Umbraco for a user's document permissions, now use Advanced Permissions.

Full Changelog: v17.4.0...v17.4.1