You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had a local storage with visibility and directory_visibility as public. When the folder was created, it strangely had other permission than we configured in permissions.dir.public. Seems like the directory visibility is ignored on creation of the PortableVisibilityConverterhere. This leads to the creation of nonexistent folders with the default visibility as private, thus a permission we did not set.
I am not sure, if that is as intended, but my suggestion would be to create the PortableVisibilityConverter with the given directory_visbility, by using it as $defaultForDirectories.
The text was updated successfully, but these errors were encountered:
We had a local storage with
visibility
anddirectory_visibility
aspublic
. When the folder was created, it strangely had other permission than we configured inpermissions.dir.public
. Seems like the directory visibility is ignored on creation of thePortableVisibilityConverter
here. This leads to the creation of nonexistent folders with the default visibility asprivate
, thus a permission we did not set.I am not sure, if that is as intended, but my suggestion would be to create the
PortableVisibilityConverter
with the givendirectory_visbility
, by using it as$defaultForDirectories
.The text was updated successfully, but these errors were encountered: