New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s3: permissions and metadata change #7422
Comments
Replying to [7422 blacktrash]:
This is a bug. |
Do you know if |
Replying to [comment:6 dkocher]:
It seems so. At least I can still control the files, even though the permissions in the console now also say:
which seems like a useless duplication. Previously:
|
In 4.4 when uploading without Preferences → Uploads → Permissions → Uploads → Change Permissions selected, the uploaded objects have only set
See also #7356. When Preferences → Uploads → Permissions → Uploads → Change Permissions is selected, the ACL set (assuming the file is world readable on the local filesystem or Others → Read is selected for custom upload permissions) is
The Fix with added canonical grantee with FULL_CONTROL for owner in 1a8c1ce. |
Since some time permissions and metada have changed.
Does not seem to affect functionality, but is it intentional?
metadata now has additional
__complete__, __service__, __user__ fields
- again: intentional?The text was updated successfully, but these errors were encountered: